|
Is this really a bug? It sounds like ACID is working correctly: Isolation so the database is in a consistent viewing state relative to the program accessing it (the view/ODP/etc). But I could be wrong. :) On Mon, 12 May 2003 22:08:30 -0400, PaulMmn <PaulMmn@xxxxxxxxxxxxx> wrote: >There was an ancient, ancient S/38 bug that sounds very similar: >Take 2 jobs. One opens the file I/O, the other Input only. Write >records through the I/O program, and you won't see the new records >with the Input access path until you close and re-open the access >path. -- "Why, you can even hear yourself think." --Hobbes "This is making me nervous. Let's go in." --Calvin loyd@xxxxxxxxxxxxxx ICQ#504581 http://www.blackrobes.net/
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.