Sergei Tigrov
Sergei Tigrov
> Also has idea create classes for each column types. In this case type casting should be implemented into this clasess. Also thought about this, looks better 👍 > These...
Realized example of creating classes for each column type with optimization of `phpTypecast()` for values retrieved from DB only ## Results for `dbTypecast()` * Current implementation **0.381μs** * Predefined methods...
What's wrong with the current type casting? https://github.com/yiisoft/db-pgsql/blob/3d47b9af600c807b981d25406ad7a02abac98ab7/src/ColumnSchema.php#L85 https://github.com/yiisoft/db-pgsql/blob/3d47b9af600c807b981d25406ad7a02abac98ab7/src/ColumnSchema.php#L107
I suppose you should use your own implementation of `ArrayParser` for these tasks in your project.
Good idea to support range types 👍 1. What about user defined range types? https://www.postgresql.org/docs/current/rangetypes.html 8.17.8. Defining New Range Types 2. You should get what you insert. Do not increment...
> 1. We need to think about this. The main problem is how to understand when it is necessary to run the data by this parser in a custom format...
> Need restore code coverage Yes, mentioned about this in the description: > Support for the `time` type with test coverage will be added after review of #230
Can be done inside `db` package by typecasting * yiisoft/db#725
Decided to use `ForeignKeyConstraint[]` instead of `arrays`. Related with #734