Re: Odd Class::DBI sequence behaviour

Class::DBI doesn't want to take control of creating new primary keys, if you use the proper subclass, in your case Class::DBI::Pg. That way, if you leave out a primary key, it assumes that the database will fill it in.

Comment on Re: Odd Class::DBI sequence behaviour

Replies are listed 'Best First'.
Re^2: Odd Class::DBI sequence behaviour by Nomad (Pilgrim) on Jan 23, 2005 at 11:59 UTC
Sub-classing from Class::DBI::Pg doesn't change this behaviour at all. And because of my particular setup using the 'set_up_table' method, doesn't work either. But I'm starting to think that this is because my tables are 'non-standard'.	[reply]
Re^3: Odd Class::DBI sequence behaviour by aquarium (Curate) on Jan 23, 2005 at 12:25 UTC
worst come to worst, do a passthrough SQL...and don't try to populate that primary key value the hardest line to type correctly is: stty erase ^H	[reply]