On Sun, 2004-01-25 at 16:31, V i s h a l Kashyap @ [Sai Hertz And Control Systems] wrote: > Dear Oliver Elphick , > > > If I am not wrong PostgreSQL select statements works on committed data > > > thus the new > > > inserted data at #3 must not be available to sai_func_b() till #5 > > > > > No. All operations by a single transaction are visible inside the > > transaction. Therefore an encapsulated function can see anything already > > done in the whole transaction. A function must be entirely inside a > > transaction and cannot start a transaction, so there can never be any > > problem about this. > > > Loads of thanks for the kind reply . > Would be greatefull if you kindly post some links/refrences to support > your answer for the said.
It's in the manual, somewhere; or try it and verify that what I say is correct. -- Oliver Elphick [EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C ======================================== "My little children, let us not love in word, neither in tongue; but in deed and in truth." I John 3:18 ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
