|
> From: rob@xxxxxxxxx > > select price into :listprice from itemmaster > where itemnumber=:itemnum > > I can just see Pluta, "I wouldn't use a cursor either, I'd use a > traditional rpg chain." :-) Doesn't it strike you as odd that you are even pre-quoting my arguments? Like, maybe you should consider using native I/O where it makes sense rather than unwavering adherence to SQL? Just a thought. As to the locking issue, there might be one other radical solution - use a client/server approach. Send requests to a data queue, let a server read it and send the result back. Sure, there's overhead, but it might be less than the overhead of opening and closing a cursor, and it would certainly keep the number of locks down. And if the logic were embedded in a server, I'd be less worried about what you actually used - native I/O, SQL, or MI, for all I care - since the code is encapsulated. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.