I missed the original question triggering this thread, so I'm not sure if the following is on target or tangential since it has nothing to do with RPC or UO .NET.
IIRC, in UV, with Transaction Logging enabled, SQL SELECT is allowed, but will implicitly do a BEGIN TRANSACTION and keep that transaction open for the duration. This, even if you merely extract data, not update. I do not know how to prevent this. As log files fill, they will remain in a "NeedSynch" state until the SQL SELECT is complete. So, if you have log files that fill within minutes, and SLECTs that run for 1 or 2 hours, you can get into trouble, filling all available logs where they cannot be saved to tape, released, and made available again. I hit this on UV10.0 running on HPUX. FWIW, cds > From: Peter Veenhof > > I'm not sure what documentation you are reading, the BASIC > documentation says you CAN execute SQL statements from within > a transaction. See page > 96 of the Basic.pdf in you documentation under the heading > Transaction Restrictions. It explicitly says you CAN EXECUTE > a SELECT. > > And I do know that my problem lies within Universe (or rather > the RPC call to universe, that's why I posted it here... It's > a bug in UO .NET.... I can do a transaction in a PICK account > using BASIC programming and have SELECT statements in it > without any problem, however doing the same from UO .NET > blows the program up. > > I'm just looking for anyone how has played with UO .NET that > might know of a workaround? > > -----Original Message----- > > It's nothing to do with .NET; it's a restriction within > UniVerse itself. > You can read about what is and isn't allowed while a > transaction is active in the UniVerse BASIC manual; it's too > long to reproduce here. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
