|[CDO/DBStore] [message #1018817]
||Thu, 14 March 2013 14:25
| Joe Sobeos
Registered: May 2012
DBStore is always generating cross (-> unnecessary joins...) tables (E1_E2_LIST) for 1:n relationships no matter if the entity is flagged as Ordered = false.
It is mapped without unnecessary cross tables if flagged as Transient (why is it stored here anyway?), but then the data is not loaded.
|Re: [CDO/DBStore] [message #1021802 is a reply to message #1021761]
||Wed, 20 March 2013 17:58
| Eike Stepper
Registered: July 2009
Am 20.03.2013 17:25, schrieb Joe Sobeos:|
>> I hoped you take the effort to describe more of your model and your application, so that I'm able to understand what
>> your problem is. But you didn't ;-(
> My problem is that CDO/DBStore does not care about performance. Especially about the count of executedsql queries.
> The "1:n relationships" implementation is only one example.
I agree, it would be awesome to have a better mapping for the unordered 1:n case. It just a lot of effort that noone has
What are the other examples?
> I don't see why you need more information about the model.
> I asked two simple questions.
> The first question is answered, but I still don't understand why CDO/DbStore is storing EStructuralFeatures flagged as
> Transient in the database.
I don't think it does and you didn't provide more evidence/infos for your assertion.
> For me Transient means do not serialize and do not store to database,
> but perhaps here I'm wrong.
Powered by FUDForum
. Page generated in 0.01956 seconds