Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COWith nHibernate you can map entities to classes in such a way that it isn't a 1:1 mapping with the db schema so you don't have to strongly couple yourself to the database. I just can't see a way at the moment of mapping multiple rows, one for each property to a single object. Typically you'd have one row which contained the data for a single object.
      singulars
    2. COI know, but i don't see any possibility to do what you want in an other way than that you already mentioned. You are able to use filter-prop on many-to-one's but imo that wouldn't help anything, also i don't think this would help to fix your performance problem anyway. Maybe i got you wrong but as i understood you are considering to refactor your eav to a relational or mixed schema. If you only keep the rare props as eavs in a bag/set you could make them lazy to only load on demand.
      singulars
    3. COThe issue is we really don't need a property bag, it's only our developers who will add new properties, we don't expect a user to extend the model. Basically the system I've inherited is built off a framework with this EAV structure in place. We want a totally normalised model going forward. I was hoping that we'd be able to perform a mapping in the way I suggested as we could then baseline the domain model and then start doing the database work. From what you are saying this isn't possible, which is a shame, as it seems the only other solution is a hand crafted DAL.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload