[fdo-internals] resetting a feature reader

[Jason Birch]

Is this risk for dirty data just for a single query or for the length of
the cached provider connection?  I'm not clear on the process.
 
If it's the latter, the this will have real implications for AVL apps
based on MapGuide where the data is changing underneath the app
constantly.
 
Jason 
 
________________________________

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Friday, January 26, 2007 11:34
To: FDO Internals Mail List
Subject: RE: [fdo-internals] resetting a feature reader


That's true if you cache the select command. Can that also happen while
you are working with a single feature reader though (and taking your
time with it while someone inserts or changes things behind your back)?
All those cases are mostly theoretical in the case of MapGuide though.
 


________________________________

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Badreddine
Karoui
Sent: Friday, January 26, 2007 2:29 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] resetting a feature reader



I can see a defect coming...what happen to those records I just
inserted? BTW. That can be an other connection/thread/process that
inserted those records.

 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20070126/75b7352f/attachment-0001.html