Skip to content

Conversation

@LorenzoPapi
Copy link

When the belongstomany attribute was given a special name, the id column type identifying wasn't working and would fall back to the usual integer id, causing errors. Now, by considering as a key the string before the :, it should work.

When the belongstomany attribute was given a special name, the id column type identifying wasn't working and would fall back to the usual integer id, causing errors. Now, by considering as a key the string before the `:`, it should work
@jasonmccreary
Copy link
Collaborator

Thank you for your PR. However, once I added the appropriate meta statement for the custom table name (e.g. users) to your sample draft.yaml file, the migrations were generated with foreignUlid() correctly. As such, I'm closing this and Issue #756.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants