Hi all,
Now that our database schema management tool is nearly ready, we can
upgrade existing databases much more easily than before.
However, since changes will be marked in the database as "applied", we need
some additional process for new databases. I'm seeing a number of solutions
here;
1. Maintain schema changes in both Pg-database.sql *and* in the changes
files in sql/changes/* and upon creating a new database, mark all changes
in sql/changes/* as "applied", assuming Pg-database and the changes are in
sync -- con: assumptions are always a risk
2. Make Pg-database into the first change and maintain all changes on top
of it, never maintaining a full schema again -- con: as time goes by,
creating a new database will take longer and longer.
3. Same as (2), but on every release, we generate a "current state" schema
dump, to speed up the creation of a new database.
Any other options?
Regards,
Erik.
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
