-
Notifications
You must be signed in to change notification settings - Fork 93
fixed missing primary key import for LazyTableReference #1231
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
Open
sinisaos
wants to merge
4
commits into
piccolo-orm:master
Choose a base branch
from
sinisaos:fix_lazytable_migration
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c435c38
fixed missing primary key import for FK migration using LazyTableRefe…
sinisaos e386495
Merge branch 'piccolo-orm:master' into fix_lazytable_migration
sinisaos cb70a52
Merge branch 'piccolo-orm:master' into fix_lazytable_migration
sinisaos 8b26a5a
Merge branch 'piccolo-orm:master' into fix_lazytable_migration
sinisaos File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this - I tested it, and it works.
I think the problem goes even deeper though.
Let's say you have this (note the
UUID
primary key):If you create the migration, it now has the import for
UUID
, but it's missing the import forUUID4
(the default value forUUID
).The problem is, we use
SerialisedTableType
, which itself callsserialise_params
. We need to access theextra_imports
from thatserialise_params
call.Sorry, it sounds very confusing.
But basically, I think the ideal solution would be this:
So we need to refactor
SerialisedTableType
slightly so can access its extra imports.Does that make sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my case everything works fine because I already tried this PR with custom primary key.
UUID4()
is imported along withUUID
with tables like this.Migration file
If you think the
SerialisedTableType
should be changed, feel free to implement it in this PR.