You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no support for longs as a type.
Using the new type system which ties everything to PHP types might make things difficult since long ints are represented as floats in php, but the datatype mysql is bigint. How would this mesh?
The text was updated successfully, but these errors were encountered:
I would think that a new datatype would have to be added that would ensure a string type in PHP consisting of only numbers (using is_numeric or ctype_digit, or a combination of the two). The type would also have to be added to the adapter.
This seems to bring up a bigger issue with the type system that I discussed with @pnomolos about the types specifying an adapter intermediate type (string, int, bingint, float, decimal, boolean, date, etc.), that then gets mapped by the adapter to a native type. This also brings up that fact that the data types need to run validation logic and set validation errors on the Entity as well. There could be a large new feature here that seems like it would solve all these issues.
I just got home from a couple weeks away and am hoping to begin some serious work on the type system that I had mentioned to @vlucas over the next week or two, which should (hopefully) solve some of the needs with the current type system, or at least be a step in the right direction :)
There is currently no support for longs as a type.
Using the new type system which ties everything to PHP types might make things difficult since long ints are represented as floats in php, but the datatype mysql is bigint. How would this mesh?
The text was updated successfully, but these errors were encountered: