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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: MikeyCarter [Submitted to the original trac issue database at 12.39pm, Monday, 16th August 2010]
I'd like to be able to dump the SQL commands used to apply a change set. That way I can insert commit points and have it skip duplicates. (in the case I need to re-apply a change set)
The text was updated successfully, but these errors were encountered:
Author: brett[at]bretth.com [Added to the original trac issue at 11.45am, Monday, 6th September 2010]
The current changeset processing code makes heavy use of the Spring framework to make database updates. Raw SQL statements to make updates are not created, instead bind variables are used to pass all parameters. There is no way to dump SQL commands with the current codebase, it would require a significant re-write.
I don't understand why you need to insert commit points and skip duplicates in order to re-apply a changeset. All changes can be re-applied with the existing implementation.
If you wish to discuss further, please post to the osmosis-dev mailing list.
Reporter: MikeyCarter
[Submitted to the original trac issue database at 12.39pm, Monday, 16th August 2010]
I'd like to be able to dump the SQL commands used to apply a change set. That way I can insert commit points and have it skip duplicates. (in the case I need to re-apply a change set)
The text was updated successfully, but these errors were encountered: