Hi,
Sorry I did not investigate properly yet. Will do it this week but one
entity looks like this:
https://gist.github.com/karlkilden/4ee0297983b659c03787
Not even sure what the purpose of @ManyToOne is. In other places we have
only @JoinColumn and it works fine also. So yeah put
Hi Karl,
Firstly Ouch, I know it is always tempting to use things like this
but I would not use it unless there was a really really good reason to
use it. It is not compatible with anything other than EL.
If your child objects start to become so many that you are thinking of
batching
What do your actual db tables and entities look like? Can you supply
some details?
Andy.
On 22/01/2015 19:10, Howard W. Smith, Jr. wrote:
Collections work well when I check isEmpty(), but I'm not using that
notation. I'm still using eclipselink 2.3.2.
On Jan 22, 2015 1:04 PM,
Hello! I think something is weird in eclipselink. I need to reproduce but if
you do select item where supplier = selectedSupplier It is one select per item
even if item only has a elementcollection with a few values...
Seems any kind of collection is unusable. Thanks for your input
Skickat från
Collections work well when I check isEmpty(), but I'm not using that
notation. I'm still using eclipselink 2.3.2.
On Jan 22, 2015 1:04 PM, karl.kil...@gmail.com wrote:
Hello! I think something is weird in eclipselink. I need to reproduce but
if you do select item where supplier =
On Thu, Jan 22, 2015 at 5:59 PM, Andy Gumbrecht agumbre...@tomitribe.com
wrote:
What do your actual db tables and entities look like? Can you supply some
details?
Andy.
On 22/01/2015 19:10, Howard W. Smith, Jr. wrote:
Collections work well when I check isEmpty(), but I'm not using that
Hello! Those of You who use eclipselink have been a real help before. How do
you manage
http://eclipse.org/eclipselink/documentation/2.4/jpa/extensions/a_batchfetch.htm
You need this everywhere to get decent behavior but it cannot be configured
globally :(
Cheers
Skickat från min iPhone
