On Monday 16 April 2007 10:01, Carl Karsten wrote: > [EMAIL PROTECTED] wrote: > > Carl, > > 1) The pk field is a postgres serial type. I assume that there is code > > in dabo to fetch the new pk value via a nextval() pass-through function. > > > > 2) Because the design specs call for it. > > So chnage it :) or does someone have a use for it? > > perhaps the right way to phrase my question is "What is the use case for > embedding the PK in that ID?" >
Actually, Larry has this wrong IMO. A sequence generator will take care of the problem. I have been away for the last week so I wasn't aware of his question. Although, it may have discovered a bug in the dbPostgres.py so it's good thing he asked. The ID that Larry is making ref to is the request of the client. The client is able to read/gather a lot of information from the id. the year, unique lot #, the species,variety, and a special two letter code. So what Larry is attempting to do is re-use the PK of the transaction. I believe this to be incorrect - we need a sequence generator for lot numbers. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
