I noticed that generated StoredProcedures.cs uses
a 'private static DataManager dm'. So how does it
support transaction for stored procedures(as static
wrapper APIs) since you cannot call 'CommitAll' from
anywhere without mod. the template code.
Also, would like to see lazy loading and caching as
implemented with Apache DB Torque project.
Thanks
from 'directxl at yahoo dot com'
Logged In: YES
user_id=1502257
The static DataManager should be changed to be accessable
and will be addressed.
You do not need to call commit all for stored procedures
because they do not retrive information into the
DataManager's DataSet.
I have partially implemented a lazy load on my business's
internal version of ORM.NET, which I will eventually move
back in to this open source version.
I would like to have better object caching to make better
use of memory and other concurrency problems, I have
thought about data caching, but that is actually less
effective as server side paging (which will be available
soon) as a performance optimizations in most cases.