On Thu, 22 Nov 2007 12:11:20 +0100 "Bart Degryse" <[EMAIL PROTECTED]> wrote: > When you use serial a kind of macro is performed: in fact an integer field is > created, a sequence is created with a name based on the table's name and the > nextval of that sequence is used as the default value for the field. Now you > have to do these steps "manually".
The second part, if you really mean the ID to be like a primary key is to put a constraint on the tables to assure that an ID in one does not exist in the other. That may sound like overkill if the situation can "never" occur but it doesn't hurt to program defensively. -- D'Arcy J.M. Cain <[EMAIL PROTECTED]> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
