ids and update it every time you took a value. (Maybe a trigger could be
used?) Due to table locking during transactions no two concurrent
requested would get the same answer. Implementation could be
interesting but relatively simple.
BEGIN;
SELECT id from unqid where name=&
On Fri, 30 May 2003, Tomas Szepe wrote:
> > [EMAIL PROTECTED]
> >
> > > Trouble is, as the rows in the tables get deleted/inserted/updated
> > > (the frequency being a couple thousand rows per minute), the database
> > > is growing out of proportion in size. After about a week, I have
> > > to r
,billingaddress,acctype,accnum)
values ('1',3639,FALSE,'','','',0,'PETER
CHILDS',0,1,0,30,15,'',5,0,0,'',FALSE,FALSE,FALSE,1,1,4133,3639,0,992);
COMMIT;
Output from script is
BEGIN
SET CONSTRAINTS
UPDATE 1
psql:crash:4: server clo
