You are a star! Thank you very much! I got so caught up looking for MySQL connection errors that I didn't think to try that.

Hi

Indicia has a system for applying database updates on the one hand and an extensible architecture on the other. What I observe is that the error is a complaint from an upgrade to the core system due to the absence of a table created by a module.

The core database updates are applied first and then the module database updates. I can see that a new install could well encounter this problem and a fix may be needed.

I haven't experienced this problem because we upgraded from version 8 to version 9 so the cache_termlists_terms table did exist for us when the core update was applied.

As a workaround, what I think you need to achieve is a change in the order with which the updates are applied. You could try the following although I may be being too simplistic.

Find the file modules/cache_builder/db/version_0_1_0/201202090851_cache_termlists_terms.sql and
  -- move it to modules/indicia_setup/db/version_0_9_0,
  -- rename it to 201312120000_cache_termlists_terms.sql
  -- then run the upgrade again.

What I am proposing with this is to move the creation of the cache_termlists_terms table in to the core updates so that it is executed immediately before the media_files.sql. It might just work.

Jim Bacon.

That's good! We made some progress. This error message can be explained in exactly the same way. The core update is trying to reference a module table that has not yet been created.

I suggest the quickest workaround for this one is to edit modules/indicia_setup/db/version_0_9_0/201403051014_cascade_on_delete.sql and delete line 42, the one which reads

DELETE FROM cache_occurrences WHERE sample_id in (select id from samples where deleted=true);

Since this is a fresh install your cache and samples tables are empty so the line is superfluous.

Re-run the upgrade after editing the file and, if we are lucky, it will now run to completion.

Jim Bacon

I observe that you are being asked to apply the update contained in modules/cache_builder/db/version_0_1_2/201308161718_map_squares_populate.

This should have been preceded by 201308161717_map_squares in the same folder which creates the table.

If we are lucky and your log level is set to debug you could look in application/logs/today's log and see the list of updates that have  been applied.

I have a hope that the map_squares update has been applied and that you could find the table if you were using pgAdmin and were to browse through the list of tables.

If that is the case then my guess would just be that we need to qualify the tables in the query you are trying to apply with the schema name as Postgres is not looking in the right place for them. Better still, set the search path to tell Postgres where to look by executing

SET search_path = indicia, public, pg_catalog;

where I am expecting indicia to be the schema name for your installation. You may even like to alter your user so that you don't need to keep setting the search path.

Jim Bacon.