On Tue, Nov 06, 2007 at 04:57:14PM +0100, Helge wrote: > gnumed_v2=# select gm.concat_table_structure(); > concat_table_structure > -------------------------------------------- > clin.clin_hx_family.clin_when::timestamptz ...
This is both good and bad news. Your schema dump contains all the tables we would expect and no more. This means you can do the following to get your bootstrapping procedure going: - go through all the update_db-vX_vY.conf files - comment out any "template version = ..." lines - set all "target version = ..." lines to "devel" This should allow bootstrapping to run through. It will show a few notes as to not being able to verify hashes but should run right through. It will (temporarily) deprive you of some of the verification checks during bootstrapping but should not otherwise degrade anything. The root cause seems to be that, indeed, your version of PostgreSQL appears to sort MD5 values differently from other versions (which is quite strange but not entirely impossible). I am working on a permanent fix. I have also improved the bootstrapper to automatically include the schema dump if it detects hash errors. So client already did so. Thanks for exposing this bug, Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
