One of the main reasons we migrated to the new query parser was to allow
for easier extension of HQL. We didn't actually make much in the way of
HQL extensions in 3.0 (except for UPDATE/DELETE, CASE and EJB-QL
functions). I've been wondering what new cool stuff we could consider
for 3.1.
Lets get aliasing in there too
select p.name as parentName ...
and either
add get methods to Query (nah)
or
add ResultTransformer support to Query results.
-max
One of the main reasons we migrated to the new query parser was to allow
for easier extension of HQL. We didn't actually make much
I have seen you already added the isInsertable and isUpdateable in the
latest cvs version.
But the lazy flag is still fixed false. This is the case for all
associations.
Could it be changed to honor the annotation setup?
Property prop = makeProperty(propertyName, value,
Mario Ivankovits wrote:
I have seen you already added the isInsertable and isUpdateable in the
latest cvs version.
But the lazy flag is still fixed false. This is the case for all
associations.
Could it be changed to honor the annotation setup?
The lazy flag for a property mean using class
Excellent, I changed that because of a JIRA bug. I did not noticed your
mail was related ;-)
My thoughts inline.
Mario Ivankovits wrote:
Hello Emmanuel!
Heres the copy from the forum:
Before I submit a patch (if needet) some little discussion please.
I made the @ManyToOne working for me after I
