9:49 a.m.
Hi,
When doing a full-text query which projects exactly one column, e.g. like
so:
List<?> list = fullTextSession.createFullTextQuery( query, MyEntity.
class )
.setProjection( ProjectionConstants.ID )
.list();
Then each list element will be a single-column array, containing the
projection result.
I'd rather have expected the list to contain the single column values
directly in this case. That's what HQL projection do and seems implied by
the docs of list().
Is it done differently in HSEARCH on purpose or should it be considered a
bug?
Thx,
--Gunnar
1:31 p.m.
I hadn't noticed that HQL projections would do that.
It seems useful indeed, but also quite irregular.. I'm not too
convinced, I guess I'd be happier if we could express the difference
on the method signature's return type.
I tend to agree that we should conform to the list() contract, but
this is unlikely to be an welcome change for existing users.
If you all agree it's an improvement, I'd schedule such an issue for 6?
Sanne
On 29 January 2015 at 08:49, Gunnar Morling <gunnar(a)hibernate.org> wrote:
Hi,
When doing a full-text query which projects exactly one column, e.g. like
so:
List<?> list = fullTextSession.createFullTextQuery( query, MyEntity.
class )
.setProjection( ProjectionConstants.ID )
.list();
Then each list element will be a single-column array, containing the
projection result.
I'd rather have expected the list to contain the single column values
directly in this case. That's what HQL projection do and seems implied by
the docs of list().
Is it done differently in HSEARCH on purpose or should it be considered a
bug?
Thx,
--Gunnar
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
3:39 p.m.
2015-01-29 13:31 GMT+01:00 Sanne Grinovero <sanne(a)hibernate.org>:
I hadn't noticed that HQL projections would do that.
It seems useful indeed, but also quite irregular.. I'm not too
convinced, I guess I'd be happier if we could express the difference
on the method signature's return type.
I tend to agree that we should conform to the list() contract, but
this is unlikely to be an welcome change for existing users.
If you all agree it's an improvement, I'd schedule such an issue for 6?
Yes, it may come at the surprise of users relying on the current behavior.
Fixing it in HS 6 seems reasonable to me.
Sanne
On 29 January 2015 at 08:49, Gunnar Morling <gunnar(a)hibernate.org> wrote:
> Hi,
>
> When doing a full-text query which projects exactly one column, e.g. like
> so:
>
> List<?> list = fullTextSession.createFullTextQuery( query, MyEntity.
> class )
> .setProjection( ProjectionConstants.ID )
> .list();
>
> Then each list element will be a single-column array, containing the
> projection result.
>
> I'd rather have expected the list to contain the single column values
> directly in this case. That's what HQL projection do and seems implied by
> the docs of list().
>
> Is it done differently in HSEARCH on purpose or should it be considered a
> bug?
>
> Thx,
>
> --Gunnar
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
3:54 p.m.
On 29 January 2015 at 14:39, Gunnar Morling <gunnar(a)hibernate.org> wrote:
2015-01-29 13:31 GMT+01:00 Sanne Grinovero
<sanne(a)hibernate.org>:
>
> I hadn't noticed that HQL projections would do that.
> It seems useful indeed, but also quite irregular.. I'm not too
> convinced, I guess I'd be happier if we could express the difference
> on the method signature's return type.
>
> I tend to agree that we should conform to the list() contract, but
> this is unlikely to be an welcome change for existing users.
> If you all agree it's an improvement, I'd schedule such an issue for 6?
Yes, it may come at the surprise of users relying on the current behavior.
Fixing it in HS 6 seems reasonable to me.
https://hibernate.atlassian.net/browse/HSEARCH-1788
3:02 p.m.
+1 for 6
On 29 Jan 2015, at 09:49, Gunnar Morling <gunnar(a)hibernate.org>
wrote:
Hi,
When doing a full-text query which projects exactly one column, e.g. like
so:
List<?> list = fullTextSession.createFullTextQuery( query, MyEntity.
class )
.setProjection( ProjectionConstants.ID )
.list();
Then each list element will be a single-column array, containing the
projection result.
I'd rather have expected the list to contain the single column values
directly in this case. That's what HQL projection do and seems implied by
the docs of list().
Is it done differently in HSEARCH on purpose or should it be considered a
bug?
Thx,
--Gunnar
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
3364
days inactive
3368
days old
4 comments
3 participants
participants (3)
-
Emmanuel Bernard -
Gunnar Morling -
Sanne Grinovero