Hi
I read through the documentation and src and noticed that Xyster_Orm is implemented as singelton. But if i subclass Xyster_Orm it would be possible to use multiple objects of Xyster_Orm.
Are there any known bugs or things which would not work as expected if i use multiple objects of Xyster_Orm?
What is the recommanded way for using Xyster_Orm in a multi user app where many concurrent logged in users should work with distinct Xyster_Orm objects (sessions)?
Thx Andy
since i'm comming from c# and
Submitted by schlachtzeuger on Tue, 08/05/2008 - 05:02
since i'm comming from c# and java i misunderstood 'static' ;)
so the thing with distinct Xyster_Orm instances per user is solved, but are there any known bugs when using more than one Xyster_Orm instance per request?
The only problem I can think
Submitted by Double Compile on Mon, 08/11/2008 - 10:01
The only problem I can think of is that the entity classes will have their metadata overwritten by the second instance (different object instances).
Any reason you need to run more than one per request?
In any case, I'm reimplementing the ORM layer currently and there won't be a problem with using more than one Orm instance other than a performance hit.
―DC
If you currently
Submitted by schlachtzeuger on Wed, 08/13/2008 - 06:15
If you currently reimplementing the orm layer may you can provide an alternative Xyster_Orm_Entity base class with witch it is possible to have properties and relations defined in the domain model and use that model without a database. cause that is such a huge drawback to have all explicitness not defiened in the model and to work with a completly empty domain model.