The function does a select to see if the id number exists, and it fails. NOT FOUND causes a RAISE EXCEPTION.
SusanOn Wed, Apr 16, 2014 at 5:05 PM, Susan Cassidy <susan.cassidy@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
SusanCould it be because the insert is done inside a function?It is a fairly large and complex Perl program, so no, not really.I do an insert via a function, which returns the new id, then later I try to SELECT on that id, and it doesn't find it.
On Wed, Apr 16, 2014 at 4:58 PM, Steven Schlansker <steven@xxxxxxxxxxxx> wrote:
>> On Wed, Apr 16, 2014 at 4:31 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
>> Susan Cassidy <susan.cassidy@xxxxxxxxxxxxxxxxxxxxxxxx> writes:
>> > Is there any way to let a transaction "see" the inserts that were done
>> > earlier in the transaction?
>>
>> It works that way automatically, as long as you're talking about separate
>> statements within one transaction.
>>
>> regards, tom lane
> On Apr 16, 2014, at 4:53 PM, Susan Cassidy <susan.cassidy@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Well, it isn't working for me right now. It can't "see" a row that was inserted earlier in the transaction. It is a new primary key, and when I SELECT it, it isn't found.
>
Can you share the code that does not work with us? Preferably as a small self-contained example.
