You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by rosselet <at...@gmail.com> on 2013/03/27 09:04:58 UTC
Re: sorting with join... probably JCR-3498 :((
It looks like I'm running into this issue:
https://issues.apache.org/jira/browse/JCR-3498
but no sign of it being fixed ... although it seems to me that this is a
pretty serious bug..
Does anyone have more info on it?
--
View this message in context: http://jackrabbit.510166.n4.nabble.com/sorting-with-join-tp4658051p4658064.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: sorting with join... probably JCR-3498 :((
Posted by Lukas Kahwe Smith <sm...@pooteeweet.org>.
On Mar 27, 2013, at 20:27 , rosselet <at...@gmail.com> wrote:
> Hi.. thanks for the feedback. I thought that SQL1 does not support joins.. I
> guess I'll have another look. Or are you suggesting a different approach?
SQL1 does indeed not support joins .. but in the few cases I at first used joins, i later realized i could just as well do without.
regards,
Lukas Kahwe Smith
smith@pooteeweet.org
Re: sorting with join... probably JCR-3498 :((
Posted by rosselet <at...@gmail.com>.
Hi.. thanks for the feedback. I thought that SQL1 does not support joins.. I
guess I'll have another look. Or are you suggesting a different approach?
--
View this message in context: http://jackrabbit.510166.n4.nabble.com/sorting-with-join-tp4658051p4658081.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: sorting with join... probably JCR-3498 :((
Posted by Lukas Smith <sm...@pooteeweet.org>.
On Mar 27, 2013, at 9:04 , rosselet <at...@gmail.com> wrote:
> It looks like I'm running into this issue:
> https://issues.apache.org/jira/browse/JCR-3498
>
> but no sign of it being fixed ... although it seems to me that this is a
> pretty serious bug..
> Does anyone have more info on it?
in general the JOIN (and SQL2) support in Jackrabbit in 2.x is sort of meh .. it mostly works but edge cases are buggy and performance is not very good. so in general i recommend to use SQL1 as much as possible. That being said Alex did have a go at several issues we pointed out.
regards,
Lukas