[dev] DB Migration questions

[Michael M Slusarz]

See, e.g.:

Quoting Michael M Slusarz <slusarz at horde.org>:

> commit e2e084a517dfe3c732b3147fddfb6d2cf481b65a
> Author: Michael M Slusarz <slusarz at curecanti.org>
> Date:   Mon May 24 17:19:02 2010 -0600
>
>     IMP tables now created via migration script
>
>  imp/docs/INSTALL                    |   14 ++----
>  imp/migration/1_imp_base_tables.php |   46 ++++++++++++++++
>  imp/scripts/sql/imp.oci8.sql        |   15 -----
>  imp/scripts/sql/imp.sql             |   15 -----
>  imp/scripts/sql/imp.xml             |   97  
> -----------------------------------

Is this the way we want to create DB's in H4?  This is *much* cleaner  
and easier than maintaining the scripts/sql directory.  The issue I  
see is upgrading from H3 though.  How does that happen?

I could see the following happening:
app/
   migration/
     1_upgrade.php  (Upgrade that occurred from App 1.1.x to App 1.2.x)
     2_upgrade.php  (Upgrade that occurred from App 1.2.x to App 2.0)
     3_new_install.php  (Create tables)

Tasks 1 (and/or 2) won't be run on a new install, since the tables  
don't exist.  And these tasks will spit informational errors if the  
upgrade has already occurred, but that should be ok (right?).

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]