-
Notifications
You must be signed in to change notification settings - Fork 46
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
Don't do 2 SQL updates per editing #11232
Conversation
3d62ecb
to
f3e639d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a complex pull request, I would like to discuss before finishing the review.
I suspect this could have some not expected or unanticipated side effects.
17917cf
to
902b118
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand things.
Note that actually we get two requests (INSERT + UPDATE or UPDATE + UPDATE) but only one commit.
You also fix another issue, conflict when table already exist in DeclarativeMeta using option keep_existing
. I would have added it in description and maybe in changelog.
Main subject could also be added to changelog IMHO.
eb65876
to
4658a01
Compare
@arnaud-morvan ready for a new pass :-) |
2774671
to
c2b403b
Compare
In papyrus there is a flush that create a first commit The idea is to update the fields in the before_* callback to avoid having tow commits
c2b403b
to
b30a45e
Compare
Be able to use existing table
Don't do 2 updates per editing:
In papyrus, there is a flush that creates a first INSERT or UPDATE
The idea is to update the fields in the before_* callback to avoid having two REQUESTS
See JIRA issue: GSSIT-114.