-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mapper relations fail when primary keys are binary #285
Comments
As said before (#197), you should use a numeric primary key with Spot.... It doesn't hurt....
|
Thank you for your Feedback, can this be a feature request ? |
It sure can be, but I don't think that's a priority for us right now. |
I will have to add this on to the ORM and create a pull request . Have made it work out of its box . |
I have not tried this, but it seems like it should be possible and a supported use case for Spot. UUIDs are valid identifiers, and are commonly used in distributed systems instead of auto-incremented ids. Can you do some digging on this @Peace-N and maybe submit a PR with the code required to support it? I don't have any system configured like this to test with. |
We are currently facing a challenge here, we are using custom types that we have registered with Dbal and the types are uuid_binary_ordered_time, the Mapper relations fail when primary keys are binary and stored in this type, infact it actually ignores.
We have tested with primary keys as strings and integeres and relations work fine. Has anyone of you ever tried this ?
The text was updated successfully, but these errors were encountered: