Martin Sommerhein wrote:
Thanks! My application will have few simultaneous users (usually just
one), but is fairly complex (in comparison to the amount of traffic).
The lack of thread safety might therefore be ok with me, since I can
"work around" it by having a giant lock. But, of course, this can be a
headache if (as) I get more traffic! Maybe I can look into it when/if
that happens and get a more fine grained locking mechanism.
I'm not really sure, but i think the trouble w/ thread is fixed right now ( fill bug about this ..), you should ask to the modeling list.
The lack of support for 'ghosting objects' is more disturbing, however.
Hum in fact, a 'ghost object' in the modeling way of life, it's a object that's been fetch from the DB, but not used anymore so it is converted in a 'ghost' (a object without any attributes and so one..) so next time you try it work with this, it will be fetch. The issue i get within my latest test ( 1 year right now) is that, there is now to ask the modeling to ghost old objects. So i need to purge editing context. Hum the main reason why i want to ghost object, is to free some memory because all users share one editing context (in my app) so in a little time i get all row as object in memory. SQLObject has this kind of trouble too. but try to answer it by random ghost (i think)
Maybe MiddleKit is the answer.
I think there is 2 majors RDBM object mapper right now : - SQLObject - Modeling
so ..
Bye bye. (again ask to Sebastien on modeling list, beside i know him, we haven't talk about that since a while).
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
