>Is there any plans to make the queries reflect the information that may
>have been previously altered within the transaction. In other words a
>hybrid union of the information within the cache and the information
>within the database.
Data (with its DBMS) often lives longer than the application access it. And,
also the data are often accessed in different way, maybe concurrently, or
even in clustering environment. I can foresee the hybrid approach associates
with complexity, a lot technical issues and is a costly resource burden,
with those requirements. Having so many request features in our list
already, passing thru queries are probably the only safe bet in this moment.
>If not would it be a project that you would
>consider opening.
It probably takes years before we reach that state. In my opinion, having
such resource into other area will be more beneficial for most people.
>Because having the queries fall through to the
>database really isn't a viable option to us and would probably stop us
>from being able to use castor in our development efforts.
Castor has an in-memory lock and cache engine to make sure least amount of
access to the database. We do have planned to optimize Castor by using less
sql join, pre-fetching and utilizes batch statement facility to speed things
up. However, passing thru queries will be there for a long while.
Thomas
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
