-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
How to override id type? #91
Comments
I think this could be a bug by looking at the generated code when id is String. The primary key is assumed to be auto generated numeric field in the where clause and table creation. Will issue a fix for this. |
Great, thanks @dukefirehawk ! |
@kevinelliott Have you tried the following annotation?
Take a look at |
@dukefirehawk Yes, when I try that, I get:
|
@dukefirehawk Any thoughts? |
OK, so turns out it was just because I was extending Model. If I remove that, it all seemingly works (thus no collision there). Hopefully I'm not missing out on anything else by not extending! |
We are currently looking into updating ORM to support models defined in multiple files. Will look into this issue together. |
Any update to this feature? Found out this was the missing info to why my attempts to create relationships was failing. Models NEEDED to be in a single file. This info should be prominent in the documentation. I was wondering how the examples were working importing private classes like:
Took me way too long to figure this out. For now I started using |
For ORM model, how do you override the id type to be UUID (String)? There is some stuff that forces id as int for query, and this is problematic.
The text was updated successfully, but these errors were encountered: