I am sorry, I should have made some clarifications about the way the wrapper is
implemented, let me answer your concerns.
I see many problems here:
* It fails if your update or delete from a different
database connection or a different process such
that the update or delete is not detected by your
wrapper.
1. there are no different database connections, the object is loaded once in
global.asa and is never closed each object loads one
database and never closes the connection, so it's a single instance for all
operations for each database used on a particular site.
* Inserts also effect the results of subsequent
queries.
2. sorry, yes inserts also trigger the refreshing of cached queries
* Updates, deletes, and inserts that are the result
of triggers will be difficult for your wrapper to
detect.
3. the method that passes the query also passes the tables names that are
affected by the query(updates/inserts/deletes)
* The code that determines what cached queries are
effected by an update or delete is likely to be
a persistent source of bugs that are very
difficult to reproduce.
that's something that might be a bit clearer now that I mentioned the setup we
already have in place
Please let me know what do you think?
-ark
>--
>D. Richard Hipp <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
