|
Hey Joel. I'm struggling upstream against the traditional record level access idea of locking the record until the update is done. I think I am making progress but thought perhaps your words would carry more weight with my fellow traditionalists than mine. Kyle On Tue, 01 Mar 2005 09:30:42 +0000, Joel Cochran <jrc@xxxxxxxxxx> wrote: > On Mon, 2005-02-28 at 21:40, Kyle Collie wrote: > > We are moving forward in exteranlizing our I/O with RPGBeans but have > > hit a snag on record locking for updates. > > > > How are you handling this? > > > > Kyle > > I'm not, I haven't seen this behavior. The idea with using SQL is that > the file is never opened for update. The only time their would be a > problem is if another program has a record opened for update in native > file access. Naturally, this goes against the idea of encapsulation. > > Can you give me an outline of the program? Maybe clarify the situation? > > Thanks, > > Joel > > _______________________________________________ > This is the RPGNext Discussion and Information (RPGNext) mailing list > To post a message email: RPGNext@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/rpgnext > or email: RPGNext-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpgnext. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.