Search Postgresql Archives

Re: Help with inventory control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Fernando Grijalba <fgrijalba@xxxxxxxxx> writes:

> Thank you for your response.
>
> I want to avoid the following situation.
>
> User1 starts order and takes the last two units.  User2 starts order 1
> minute after and checks inventory. He sees 2 units left and adds them to
> the his order.  User1 commits his order.  Now User2 cannot finish his
> order because the products are not available anymore.
>
> This is the problem I want to avoid.  Therefore if User1 takes the product
> but does not finish the order I want the inventory to still show that the
> product is sold out to other users.
>
> Any suggestions on how to implemnt that?

I think just using SELECT FOR UPDATE should solve this problem--it
will lock the row and SELECT FOR UPDATE in the second transaction
won't return until the first transaction commits.

-Doug

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux