Search Postgresql Archives

Re: Database Insertion commitment

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

 



On mán, 2007-07-09 at 03:34 -0400, Jasbinder Singh Bali wrote:
> My scenario is something like this. I'll try to make it modular and
> simple.
> 
> Start Function A (Written in plperlu with no subtransactions)
>      Insert 1 on tbl_abc; (fires trigger A)
>      Insert 2 on tbl_abc; (fires trigger A) 
> End Function A
> 
> Start Trigger A
>        check the value of col_abc in tbl_abc
>        Start Activity A if col_abc in tbl_abc doesn't is not
> duplicated.
> End Trigger A
> 
> Now, if Insert 1 inserts col_abc  = 'xyz' in tbl_abc 
> and Insert 2 inserts the same value of col_abc ='xyz' the its not able
> to see the value of insert 1 
> and erroneously starts Activity A that it should not actually.
> 
> Do you think I am missing something vital here? 
> I'm kind of stuck and confused because fundamentally Insert 2 should
> be able to see the value of Insert 1 as there is no subtransaction
> involved.

maybe you should provide us with a simple test case, to illustrate your
problem.

gnari




[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