[dev] [cvs] commit: nag/scripts/upgrades convert_datatree_shares_to_sql.php ingo/scripts/upgrades convert_datatree_shares_to_sql.php mnemo/scripts/upgrades convert_datatree_shares_to_sql.php turba/scripts/upgrades convert_datatree_shares_to_sql.php kronolith/scripts/upgrades convert_datatree_shares_to_sql.php

[Michael Rubinsky]

Quoting Jan Schneider <jan at horde.org>:

> jan         2009-07-20 07:16:56 EDT
>
>   Modified files:        (Branch: FRAMEWORK_3)
>     scripts/upgrades     convert_datatree_shares_to_sql.php
>     scripts/upgrades     convert_datatree_shares_to_sql.php
>     scripts/upgrades     convert_datatree_shares_to_sql.php
>     scripts/upgrades     convert_datatree_shares_to_sql.php
>     scripts/upgrades     convert_datatree_shares_to_sql.php
>   Log:
>   How was this ever supposed to work? Fix sequence name, catch errors.

We didn't originally have MDB2 use 'id' as the sequence name, when it  
was first released it used the default MDB2 value (seq?). It wasn't  
until 3.3 that we changed the field name to 'id' since MDB2_Schema  
couldn't upgrade the schema with mixed sequence names. This is what  
the fix_mdb2_sequence upgrade script was for.


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org

"Time just hates me. That's why it made me an adult." - Josh Joplin