You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really like this package and have used it in many different projects with no issues, so first of all I would like to thank you for developing and sharing it.
I recently came across an issue where a composite primary key was causing an exception when attempting to evolve, despite having made no changes to the relevant class.
The relevant part of the schema looks something like this:
Hello,
I really like this package and have used it in many different projects with no issues, so first of all I would like to thank you for developing and sharing it.
I recently came across an issue where a composite primary key was causing an exception when attempting to evolve, despite having made no changes to the relevant class.
The relevant part of the schema looks something like this:
and the exception:
I have found a satisfactory work-around by altering
MyTable
to use a standard primary key, and a separate uniqueness constraint:However, it would be nice if evolving composite primary keys worked without issue, too.
The text was updated successfully, but these errors were encountered: