For all Queries the Dataobjects are in a updatable state
until the datacontext is commited or rolledback.
Here I suggest the main problem.
My main web-application based on cayenne, is also readonly,
but I have decided for a session based context ... to be save.
cayenne-use..bjectstyle.org schrieb am 04.03.05 16:18:38:
>
> Hi there!
> I am currently developing a web application using Cayenne that makes
> read-only accesses to a database, with a Level 1 caching (no cache sharing).
> I am thinking about a way to have only one DataContext serving only one
> ObjectStore so every user would then benefit from everybody's past
> requests.
>
> Is it possible and a good idea to change a Session-Bound DataContext to
> an Application-Bound DataContext or should I stick to session-bound
> datacontexts ?
> If yes, how can I do it and is it thread-safe? How to prevent the cache
> from growing infinitely?
>
> Also, our database will also be frequently updated by other
> applications... How can the datacontext be aware of those changes?
>
> Thanks in advance...
>
> --
> Julien Vignali
> julien.vignal..im.hcuge.ch
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
This archive was generated by hypermail 2.0.0 : Sun Mar 06 2005 - 04:53:05 EST