13 Jun
2006
13 Jun
'06
8:07 p.m.
Mark,
openser provides by default DB conf that works - mainly to avoid common
problems with users mixing different versions of DB installations with
other versions of openser installations.
That's an important requirement - make it work in the simplest way for
most of the users, even if beginners.
Now, if somebody, wants to set different tables, of spread the tables
across different DBs, it means he knows what he is doing and
automatically he should take care of versions. Also the version
mechanism is the last alarm for such situations. If you changed the DB
scheme, the version issue should make you aware that you need to be
careful with the changes and to respect the table formats.
regards,
bogdan
Mark Kent wrote:
>in order to
work, the table has to contain the version required by the
>installed openser - check openser_mysqldb.sh (after installation) or
>scripts/mysqldb.sh in sources.
>
>
Thanks for the explanation, but I think you missed the point.
The 'domain' module (and other modules) allows one to specify the
table to be used and even to specify a comletely different database on
some remote server to be used... one that is different than that
"used" at install time (when the user may not have even intended to
use that module, but was just executing the script blindly).
If a user does subsequently specify a different db_url or change the
name of the module-specific table, then the openser code has no
business checking against a list of static version numbers.
The user has over-ridden the default behaviour with his settings
and is saying "I'm not using the default tables built at install time..."
Unless, of course, the user should update this 'version' table manually.
If that's the case, then the module documentation should make note
of this in every module where the db_url is documented.
Thanks,
-mark