X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=VERSIONING.SKETCH;h=03e6ea116d12da83cf2da865894539bccd18b0b7;hb=2fef093d6dd0a13c6ecc2fff1f3089add0b97484;hp=bf0436a45317990e0a30b5e648b3a2f126d3d879;hpb=4386b954f6f1d4f2046b7827375c58f4e402f586;p=dbsrgits%2FDBIx-Class.git

diff --git a/VERSIONING.SKETCH b/VERSIONING.SKETCH
index bf0436a..03e6ea1 100644
--- a/VERSIONING.SKETCH
+++ b/VERSIONING.SKETCH
@@ -4,12 +4,9 @@ Schema versioning/deployment ideas from Jess (with input from theorbtwo and mst)
  - create an SQL file, via SQLT, for the current schema
  - passing prev. version + version will create an sqlt-diff'ed upgrade file, such as
   - $preversion->$currentversion-$dbtype.sql, which contains ALTER foo statements.
-DONE
 2) Make deploy/deploy_statements able to to load from the appropriate file, for the current DB, or on the fly? - Compare against current schema version..
 3) Add an on_connect_cb (callback) thingy to storage.
-DONE
 4) create a component to deploy version/updates:
- - is injected into the Schemas base classes
  - it hooks itself into on_connect_cb ?
  - when run it:
    - Attempts or prompts a backup of the database. (commands for these per-rdbms can be stored in storage::dbi::<dbtype> ?)