Personally I find that to be too much work to set up.
On Wed, Nov 18, 2015 at 2:52 AM Gunnar Morling wrote:
> +1 it's a useful thing.
>
> Instead of using Strings to identify loading groups, would it be
> better to use class literals? It'd prevent wrong loads due to typos
> and would help to id
+1 it's a useful thing.
Instead of using Strings to identify loading groups, would it be
better to use class literals? It'd prevent wrong loads due to typos
and would help to identify the attributes of one group e.g. in the
IDE. But it would add the overhead for defining the groups:
public in
Hi,
Sounds like a good idea. I like the lazy fetch profiles. Previously it
required the Blob to be moved to a different table.
Vlad
Vlad
On Mon, Nov 16, 2015 at 11:09 PM, Steve Ebersole
wrote:
> Regarding HHH-10267...
>
> 5.1 will include a new feature allowing users to specify groups for
>
Regarding HHH-10267...
5.1 will include a new feature allowing users to specify groups for
(bytecode enhanced) lazy attribute loading. In the original support
accessing one of these lazy attributes forced them all to be loaded[1].
For example...
@Entity
public class Company {
...
@Basic(
