I did state in my OP that I was using "Postgre", and the PRIMARY KEY assignment is done further down in the SQL dump, in typical Postgresql fashion.
ALTER TABLE computer ALTER COLUMN compid SET DEFAULT nextval('computer +_compid_seq'::regclass); ALTER TABLE customers ALTER COLUMN uniqid SET DEFAULT nextval('custome +rs_uniqid_seq'::regclass); ALTER TABLE ONLY computer ADD CONSTRAINT computer_pkey PRIMARY KEY (compid); ALTER TABLE ONLY customers ADD CONSTRAINT customers_pkey PRIMARY KEY (uniqid); ALTER TABLE ONLY customerstocomputers ADD CONSTRAINT customerstocomputers_pkey PRIMARY KEY (custid, comp +id); ALTER TABLE ONLY customerstocomputers ADD CONSTRAINT customerstocomputers_custid_fkey FOREIGN KEY (custi +d) REFERENCES customers(uniqid); ALTER TABLE ONLY customerstocomputers ADD CONSTRAINT customerstocomputers_compid_fkey FOREIGN KEY (compi +d) REFERENCES computer(compid);
In reply to Re^2: Catalyst and DBIC, lookup table question
by vendion
in thread Catalyst and DBIC, lookup table question
by vendion
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |