[DMIG-26] Remove implicit schema diff to sql in Migration tasks for explicit solution Created: 16/Nov/11 Updated: 21/Nov/11
|Reporter:||Benjamin Eberlei||Assignee:||Benjamin Eberlei|
Currently the following leads to an implicit drop table statement:
However this should be an explicit operation that internally puts everything onto the "addSQL" stack, then resets the schema diffs to zero by cloning the current schema into the "diff schema" again.
|Comment by Beau Simensen [ 20/Nov/11 ]|
So each call to syncSchema() would result in processing all changes on the schema instance (dropTable(), etc.) to actual SQL commands and placed on the "operations" stack? And at that point the schema instance should show no diffs so that any future calls to syncSchema() would only include schema changes since the previous call?
|Comment by Benjamin Eberlei [ 20/Nov/11 ]|
|Comment by Beau Simensen [ 21/Nov/11 ]|
Alright, I'll see what I can do. I have a feeling I will get a pretty good idea how everything works if I start digging into this one.