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
problem when table has FK to itself #39
Comments
Hi there @ryanbarry The problem here is that we treat We could consider Thanks for using sqlboiler! |
Hi @ryanbarry, is there a particular reason you are not using your unique uuid as your primary key, opposed to the serial id, or vice versa? |
@ryanbarry we've added uuid to the trim suffixes in the dev branch. Once these are merged into master (hopefully today) then you should not need to change any code, as long as you update your sqlboiler and regenerate. |
this is awesome, i really appreciate the quick turnaround! reason for having serial id & unique uuid is to expose uuid as an external identifier while keeping the serial id as internal to our datastore, while keeping querying simple. thanks again 😃 |
Hey @ryanbarry, 2.0.1 has been released which includes the fixes for the issues you were having. Thanks. |
- There was no thought put in if a relationship struct already existed when it went to be used a second time so it was being clobbered. - Fix #39
i've got the following table (postgres):
but the generated code gives the following errors when building:
am i doing something wrong? is there a way to name things that won't cause this problem? Thanks in advance! Other than this minor issue, I'm really enjoying using this!
The text was updated successfully, but these errors were encountered: