Sergei Tigrov

Use case for the current implementation of `where()` ```php $query = (new Query($db))->from('table_name'); foreach ($list as $item) { $count = $query->where(['field' => $item])->count(); ... } ``` For the issues, renaming...

The second suggestion looks good. ```php foreach ($list as $item) { $count = $query->resetWhere()->where(['field' => $item])->count(); ... } ```

Good, I implement

In version 1.1.0 can be realized in `AbstractSchema` without adding the methods to `SchemaInterface`. Then add the methods to the interface in version 2.0.0

Why should it accept `Stringable` objects? Just use it as `$constraint->name((string) $stringable)` and accept `string|null $value` only

For internal initialization `string` is enough. Some class instances are initialized only in the package.

2. This is almost the same case as case 3, but we can get fields from table schema for casting type of values If no colums passed then means columns...

> But why need columns in this case? Isn't that the equivalent to way 3? Columns are needed for type casting and seems not all DBMS supports partial lists of...

This method has one advantage. If the logger or profiler is configured on the same db connection, the logger and profiler entries will be rolled back along with the failed...

Looks like predefined constants with appropriate values for each DBMS are needed. Related with #659?