28 Feb
2008
28 Feb
'08
12:47 p.m.
Hi Iñaki,
The DB migration script (from 1.3 to 1.4) will just not migrate these
removed columns in the new DB. Of course you can move them manually if
interested in maintaining them.
In the devel version, the change affects directly (openserctl script)
the db_text support as the columns from the subscriber table are
addressed by index, instead of name....
Regards,
Bogdan
Iñaki Baz Castillo wrote:
El Wednesday 27 February 2008 10:10:31 Bogdan-Andrei
Iancu escribió:
Hi Jonathan,
More or less this is the whole idea - many openser admins configures a
different additional set of fields in the subscriber table, based on the
needs of some provisioning tools.
Of course, we cannot find a common set for this extra (non-openser)
fields, so the most clear way to do it is to keep in the openser default
DB struct only the fields that are used by openser. Then, anybody may
"customize" the tables, based on his particular needs, without
conflicting with the "particular" needs of somebody else ;)
I agree 100%.
Just a question: what about OpenSer upgrading? will the upgrade script need to
re-create the subscriber table (so remove the custom colums added by the
user)?
Regards.