oqgraph-dev team mailing list archive
-
oqgraph-dev team
-
Mailing list archive
-
Message #00068
Re: v3 ORDER BY
Hi Antony
> This is probably more to do with rnd_pos() and position().
> if ref_len is made long enough to encode a row, then we can fudge it.
You appear to be speaking English, but the above is not clear to me.
I'll create a bug report for it: https://bugs.launchpad.net/oqgraph/+bug/1133093
It's critical, as we must order by seq to get a correct path (the fact that usually the output is already ordered that way is a sideline - rows have no order so ORDER BY is necessary).
> On 24 Feb, 2013, at 10:45 pm, Arjen Lentz wrote:
>
> > SELECT * FROM graph WHERE latch=1 AND origid=1 AND destid=6;
> > works
> >
> > SELECT * FROM graph WHERE latch=1 AND origid=1 AND destid=6 ORDER BY
> > seq;
> > segfaults.
> >
> > What I actually tried first (to be a bastard) was ORDER BY seq DESC,
> > which crashed, but since ascending also crashed the bug might have a
> > different cause.
> >
> >
> > --
> > Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
> > Australian peace of mind for your MySQL/MariaDB infrastructure.
> >
> > Follow us at http://openquery.com/blog/ &
> > http://twitter.com/openquery
> >
--
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Australian peace of mind for your MySQL/MariaDB infrastructure.
Follow us at http://openquery.com/blog/ & http://twitter.com/openquery
References