Hi Leo,
I believe that error is related to a fairly old SQL update script from one of our modules, which your local instance must be running. That constraint should have been created by EHR_ComplianceDB-0.00-11.20.sql, and later dropped in EHR_ComplianceDB-12.34-12.35.sql. I assume that's the script that's failing. I'm not sure why your instance would be in this state, but it sounds like that constraint was never created. I think there are a couple options:
1) Completely remove the EHR_ComplianceDB module from your local server. This would allow the server to start, since it would no longer try to run that SQL upgrade script. If you do this, once the server starts I would recommend going to the admin console, clicking on the 'Module Details' link (near Module Information). From this page, find EHR_ComplianceDB and pick the 'delete module and schema' option. This will drop that module, schema, and the other installation-related information stored in your DB. This means should you ever encounter that module again (like the next time you update from trunk), it should do a clean install, which is running normally.
2) If this is a dev machine, you could go into PG Admin and manually create that constraint along with any other missing SQL that was not run. This is sort of a hack and I would only ever try this on a dev machine. I also hesitate to try to go this route, since it might take some knowledge of the SQL upgrade scripts. I think the option above would be simpler and less prone to error.
-Ben |