-
Notifications
You must be signed in to change notification settings - Fork 125
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
version.changeset
seems to be broken on postgresql native versioning
#117
Comments
I guess this is because the triggers do not implement the |
I changed the strategy globally to |
I'm also having problems in changeset using native versioning, but my changeset for subsequent versions is not empty, it has all the same fields again, like the insert operation.
Note that only |
I've tried the subquery strategy, it does work for the first change, but the second one got the changed field from the first change...
I've changed What could I do to fix this? Any help much appreciated. |
version.changeset
sort of works onOperation.INSERT
, but all subsequent versions havechangeset
{}
The text was updated successfully, but these errors were encountered: