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 have created an experimental branch compatible with the up-to-date schemacrawler version 16.x. It manages to run our private test suite successfully, however it introduces subtle backwards incompatibility of the generated classes (I'm not sure if it is feasible to avoid this).
The undesired change is detected by failing CodeGeneratorTest pointing to an unexpected serializedTableModel value and in practice I noticed it manifests as different ordering of arguments in generated methods (e.g. RedG.addUserRoleAssignment(User, Role) vs RedG.addUserRoleAssignment(Role, User))
I have created an experimental branch compatible with the up-to-date
schemacrawler
version16.x
. It manages to run our private test suite successfully, however it introduces subtle backwards incompatibility of the generated classes (I'm not sure if it is feasible to avoid this).The undesired change is detected by failing
CodeGeneratorTest
pointing to an unexpectedserializedTableModel
value and in practice I noticed it manifests as different ordering of arguments in generated methods (e.g.RedG.addUserRoleAssignment(User, Role)
vsRedG.addUserRoleAssignment(Role, User)
)If anybody finds this useful the code is available here: https://github.com/robokaso/redg/tree/schemacrawler16
The text was updated successfully, but these errors were encountered: