I did some testing and there does seem to be some buffering going on with ACE OleDb. I found that
-
If I did some INSERTs and then immediately did a SELECT on the same OleDbConnection the new rows were available right away.
-
If I opened two OleDbConnection objects, INSERTed on
con1
, and then immediately SELECTed oncon2
the new rows took approximately 5 seconds to become available on thecon2
connection. -
If I opened two OleDbConnection objects, INSERTed on
con1
, didcon1.Close()
, and then immediately SELECTed oncon2
the new rows were available right away.
So, it appears that closing the OleDbConnection has the effect of “flushing” the writes and making them available to other connections sooner. My guess is that OleDb is implicitly buffering (or “batching”) updates because ACE/Jet is a shared-file database and it is trying to reduce the contention on the database file.
(When I did the same test using SQL Server there was no significant difference between the case when I closed con1
and the case when I left it open. In every case the new records were available instantly.)