Hi Brett,
On Thu, Dec 6, 2012 at 9:44 PM, Brett Meyer wrote:
> We're still aiming to have the 4.1.9.Final release next Wed. (12/12/12).
> Please let us know if there are any objections or reasons to hold off.
Any chance we could make progress on
https://hibernate.onjira.com/browse/HHH-7829 bef
We're still aiming to have the 4.1.9.Final release next Wed. (12/12/12).
Please let us know if there are any objections or reasons to hold off.
And no, the world possibly ending on 12/21 isn't a reason ;)
Brett Meyer
Red Hat Software Engineer, Hibernate
+1 260.349.5732
Personally I think it is maybe better to getting it working first the
way the persisters expect it currently. Addressing changes inside the
persister is a next step, but I did not want to "dirty the waters" in
terms of trying to implement this new metamodel while both the producers
and consume
having a design question, how should we model this
(correct me if I get this wrong)
for this inheritance hierarchy, the relational model of root entity is pushed
to the sub entity, so the table of sub entity has all "root table" columns / pk
and depends on if root entity is abstract, there may o
On Dec 6, 2012 7:43 AM, "Emmanuel Bernard" wrote:
>
> My fear was simply that TypeDescriptor was a class hosted on Hibernate
> ORM's codebase. But in retrospect I made that up on my own.
>
> If we have access to the type information via a given class - say
> TypeDescriptor - and that TypeDescript
My fear was simply that TypeDescriptor was a class hosted on Hibernate
ORM's codebase. But in retrospect I made that up on my own.
If we have access to the type information via a given class - say
TypeDescriptor - and that TypeDescriptor is hosted on the query parser
project then, we don't have a
