Optimizing where schema is stored

[nguyenk]

Schema is stored in a file inside the package, meaning, if I remove the package I loose the shema file, and next time I will register a DB patch, it will create a complete DB creation patch.

Quick Solution : store if in mouf/no_commit, or in any unversionned file/folder INSIDE the project

Clean Solution : TDB :). Maybe the best is storing it in database...

[xhuberty]

As we want to dissociate package from Mouf framework the quick solution will not implemented.
We still need to work on it to find the best solution since this package will help all DataMapper ORM user.

[moufmouf]

As we want to dissociate package from Mouf framework the quick solution will not implemented.

So far, the database.patch package is very much linked to Mouf (because it massively uses instances to register patches and because it is heavily based on the UI to register a new patch). I mean: we don't really have a way to register a patch out the UI.

So I'd still be ok to move the patch file to mouf/no_commit (if the directory exists), with a fallback to the package directory maybe?

Yet, I was thinking about something a bit different. I think we should create a completely new patch type that stores a complete DB model instead of just some SQL. Bonus: we should have a UI (using Vue or Angular) that let's us create/add/modify tables.

When applying the patch, a diff is made with the current model and the diff is applied.

What do you think?