Thanks a lot. There is so much buried in those frameworks and many things are
realy obscure in themselves
---markus---
> On 2 Apr 2017, at 01:35, Ricardo Parada wrote:
>
> Hi Markus,
>
> I ran into that problem before with a restricting qualifier in one of our
> entities. I fixed it by doin
Hi Markus,
I ran into that problem before with a restricting qualifier in one of our
entities. I fixed it by doing what Fabian suggested.
Ricardo
> On Apr 1, 2017, at 2:18 AM, Fabian Peters wrote:
>
> Hi Markus,
>
> To me it looks like you're getting bitten by the
> "applyRestrictingQuali
Hi Markus,
To me it looks like you're getting bitten by the
"applyRestrictingQualifierOnInsert" feature:
## Specifies that you want restricting qualifiers "applied" to your newly
## inserted objects. For instance, if you have an entity that is part of
## single table inheritance and your restri
In a large project we have used "extends EOGenericRecord" in our _Entity.java
templates.
Just recently we wondered why (probably just an oversight) and changed that to
"extends ERXGenericRecord". Don't see any reason why this should not work.
One of our entities (ElectronicDocument) in the eomo
