Ticket #445 (closed defect: invalid)

Opened 7 years ago

Last modified 1 month ago

dbdo fails to generate entities for pgsql

Reported by: jsheth Assigned to: jsheth
Priority: normal Milestone: 0.4.8
Component: SGL - Install Severity: major
Keywords: Cc:


If you check out the 0.4.x stable branch from SVN, the var/cache/entities/ directory is empty. This prevents the user from logging in, and Seagull fails with the error that says Login.php could not be found.

Solution: pre-populate and check in these missing files, which are generated by DB_DataObject.

Change History

02/03/06 14:54:38 changed by jsheth

Oops - I think I made a mistake here in my original description. For whatever reason, the installer did not create these files (unless I failed to check the correct option during installation).

02/03/06 15:13:38 changed by jsheth

I get the following error when I try to log in:

DB_DataObject Error: Unable to load schema for database and table (turn debugging up to 5 for full error message)

02/03/06 16:15:27 changed by jsheth

Workaround (Thanks to AJ):

Copy Module.php from an existing entities dir into the entities dir first

Disable authorization in var/<sitename>.default.conf.php and goto index.php/maintenance/action/dbgen

Click on 'rebuild dataobjects'.

I am not sure why the installer did not do this ... ?!

02/05/06 08:17:55 changed by demian

  • owner changed from somebody to jsheth.

hiya jsheth

you need to point out that you're using pgsql, not many users are and they don't get this prob. i just installed pg recently, not sure if i will get time to look into it, but i can guarantee prob will be a constraint failure, therefore sql loading failure, therefore db_dataobject loading failure. let me know if you find the particulars.

02/05/06 08:18:44 changed by demian

  • component changed from not categorised to SGL - Install.
  • summary changed from For 0.4.x stable SVN branch, var/cache/entities/ is empty to dbdo fails to generate entities for pgsql.

02/05/06 22:13:04 changed by jsheth

Hi owner/Demian,

Yes this occurs on PostgreSQL. Sorry, I should have mentioned that. I will investigate this problem, and try to find out which constraint is failing, and how to fix it. Thanks for categorizing it.

My other (redone) patches for 0.4.8 are on the way. I will open tickets as necessary for each bug fix and corressponding patches.

02/06/06 12:52:14 changed by jsheth

  • severity changed from normal to major.

01/03/13 12:03:38 changed by demian

  • status changed from new to closed.
  • resolution set to invalid.