On Thu, 28 Jan 2010, Victor Engmark wrote:
> Otherwise I guess we'll have to parse
> tabcreate.sql to make sure we get all of them. 

All the ones from tabcreate.sql are in tabdrop.sql.  The problem is with
dynamic tables, created on run time by the admins, such as new ``book
price'' index, etc.  See my other email.

> I guess I'd vote to drop the schema anyway, since auxiliary tables
> should be in a different schema to avoid namespace collisions when
> upgrading.

This would be dangerous, since some Invenio installations can choose
storing their custom tables we don't know anything about.  E.g. some
Invenio installations use their own submission systems, not WebSubmit.
inveniocfg --drop-tables should drop only tables managed by Invenio
core.

Best regards
-- 
Tibor Simko ** CERN Document Server ** <http://cds.cern.ch/>

Reply via email to