Use mem migrations to build models on WASM #411
Draft
Conversation
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
jayvdb
force-pushed
the
wasm-build-using-mem-migrations
branch
2 times, most recently
from
2fe575b to
a82b47b
Compare
jayvdb
changed the title
jayvdb
force-pushed
the
wasm-build-using-mem-migrations
branch
2 times, most recently
from
820470a to
f080067
Compare
jayvdb
force-pushed
the
wasm-build-using-mem-migrations
branch
from
f080067 to
5e30787
Compare
Collaborator
Author
|
fwiw, I know what the problem is with the newtype example, but as is often the case, it is going to require enhancing the migration generator, specifically supporting converting a primary column from pg bytea to jsonb, whilst there are foreign key references to it. I'm half way there .. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Sits on top of #410
A bit more controversial, but IMO worth the pain.
Notably this doesnt allow models to be referenced before they appear in the source, hence the change to getting_started models order. And thus no circular models. We can document these as part of the many limitations for the WASM target.