My fatal error has got me thinking about backup/restore, particularly in a online production environment [I'm running on a local server for evaluation].
The Catalog guide recommends user's catalog tables being prefixed with cat_ otherwise the a TL system upgrade will wipe the data. I took a backup using the backupDB extension but on restore I got:
I deleted the TL database and recreated an empty schema and tried again:Fatal error: Uncaught exception Exception with message Query error: Duplicate entry '7' for key 1 (INSERT INTO `cat_fobmcp_observations ....
So some other means will have to be used (e.g. MySQL Admin). But it looks like the Catalog extension has its own tl_ prefixed tables that appear to refer to the cat_ tables. So any backup of the _cat tables has to be synchronised with a backup of the tl_ tables. And similarly on restore. I think this mix backup/restore is prone to error and my bet is that it is best to use a single backup/restore which will have to be MySQL Admin [my ISP only allows this].Fatal error: Uncaught exception Exception with message Query error: Table 'typo.cat_fobmcp_observations' doesn't exist (INSERT INTO `cat_fobmcp_observations` ............
However, should there be a system upgrade then after the upgrade I need to:
a) restore my cat_tables - I could edit the sql file from a pre-upgrade backup and just keep the cat_ tables
Will I need to restore
- b) the tl_ tables that are associated with catalog and have references to my cat_ tables - which ones?
[/*:m:2hi4khx5]- c) the tl_ tables that are associated with taxonomy - which ones?[/*:m:2hi4khx5]
or will the content of these be preserved by the system upgrade?
Have I understood this correctly? Is there a better strategy?
Bookmarks