good chemistry is complicated,
and a little bit messy -LW
dbicdump not importing the full table (Postgres)by kiz (Monk)
|on May 08, 2012 at 11:37 UTC||Need Help??|
kiz has asked for the
wisdom of the Perl Monks concerning the following question:
Environment - Perl: Ububtu 12.04; Perl 5.14.2; all packages installed via .debs. Database: postgres database on a Sun server.
I am using dbicdump to create a pile of DBIx::Class packages to access a database... and a few of tables are not coming through cleanly.
For example - If I query my database through psql, I get:
When I run the following dbicddump commanddbicdump -o dump_directory=./lib/perl -o debug=1 EDINA::ORI dbi:Pg:dbname=oarj3;host=[host];port=[port] [username] [password]
I get the following extract in Url.pm:
First off.... the column "tbl" has become "table", and unaccessable - which is a bit of a problem, but easily solvable.
However the bigger problem is that I'm missing 7 columns!
The interesting part is that this is happening to my 'urls' table (12 rows), my 'name' table (drops the final "pri" column), and my 'org' table (8 rows: drops 6!), but not my 'repo' table (15 columns) or my 'sword' table (6 columns)
I've looked at the debug output, and it doesn't seem to be listing the columns:
Just to add confusion here - I've another database (same name) on a different postgres server (different port), and I know it's not being referenced as it has different fields in its tables, and they're not being imported.
I've looked and looked, rerun and compared, and even spoken to a teddybear.... Other than hand-coding the missing data into the records, is there something I've missed?
Is there an obvious reason the data is not being build correctly?
-- Ian Stuart
A man depriving some poor village, somewhere, of a first-class idiot.