Alan Acosta wrote:
> But i have a new problem there, i have no rows for update, i create new rows
> when the seats are sold, cause rarely the database knows the capacity of the
> bus, number of seats, even some bus doesn't have seat number 4 for example
> :p. So i cannot SELECT FOR UPDATE no existent rows, but i still need to lock
> in some way in order to check if seat number X was already sold or is free !
Sounds like you need a uniqueness constraint of some sort to detect when the
seat has been sold already when you try the insert.
In response to
pgsql-general by date
|Next:||From: Alban Hertroys||Date: 2011-02-28 22:44:10|
|Subject: Re: Transactions and ID's generated by triggers|
|Previous:||From: Alan Acosta||Date: 2011-02-28 22:39:07|
|Subject: Re: Lock ACCESS EXCLUSIVE and Select question !|