Should I assemble a feature in JIRA?
Btw, if this is double-posted again, I'm sorry, but I don't know why it
keeps happening to me in this list.
Regards,
Marek
On 07/11/2011 10:10 PM, Mike Kienenberger wrote:
For what it's worth, functions in order by is now supported by the JPA
reference i
For what it's worth, functions in order by is now supported by the JPA
reference implementation, as of 14 months ago.
-- Forwarded message --
From: James Sutherland
Date: Tue, May 4, 2010 at 2:42 PM
Subject: [eclipselink-dev] SVN commit trunk: bug#219814 JPQL enhancements
To: "
Is there a way to make the modeler ignore existing DB tables that I
don't want it to touch, during reverse engineering and (especially)
migration? I have a unique business constraint that requires me to
create a schema within an existing database, even though the new
tables have no relationships wi
Heh :-)
In 3.1 we have a nice mechanism for creating simple extension points of
Cayenne. I hope we'll start using that more to unwind these chains and allow
for easier extensibility. I guess community input and contributions should
become a driving force here.
Andrus
On Jun 30, 2011, at 4:0
Sigh... I feel like we should've used common sense and built our own QL based
on EJBQL/JPQL instead of blindly following the JPA spec. Which among other
things says "The Java Persistence query language includes [...] built-in
functions, which may be used in the WHERE or HAVING clause of a query.
Hi all,
I was trying to push a query through parser today and it didn't make it.
"SELECT stt FROM SubTaskType stt ORDER BY ABS(stt.code) ASC"
Exception is below, my question being whether it is correct behaviour or
a bug. I know mysql allows such syntax and oracle too (it allows numeric
sorti
