Re: [sqlite] parser stack overflow in view

Finally it works and fast again :-) It was possible to execute some parts before. Thanks to all helpers > Gesendet: Montag, 04. August 2014 um 14:26 Uhr > Von: "Clemens Ladisch" <clem...@ladisch.de> > An: sqlite-users@sqlite.org > Betreff: Re: [sqlite] parser stack

Re: [sqlite] parser stack overflow in view

Michael wrote: >> Von: "Richard Hipp" >> The LALR(1) parser stack is limited to a depth of 100, by default. > > Ok thanks. I reduced it by one subquery to be conform with standard builds. The parser has different limits than the SQL execution engine. You could simply move some

Re: [sqlite] parser stack overflow in view

quot;Richard Hipp" <d...@sqlite.org> > An: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> > Betreff: Re: [sqlite] parser stack overflow in view > > On Tue, Jul 29, 2014 at 5:00 AM, Michael <ruther1...@gmx-topmail.de> wrote: > > > I ha

Re: [sqlite] parser stack overflow in view

On Tue, Jul 29, 2014 at 5:00 AM, Michael wrote: > I have a view with about 6 Unions and a depth of about 6 subselects in > each select. > Shouldn't be a big thing and it was no problem with sqlite 3.7.17. > Since 3.8 (3.8.4.3) I get "parser stack overflow". I have many

Re: [sqlite] parser stack overflow in view

> > ) > >) > > ) ) and category.zone in (select zone from zones where zones.zones=1) > ) > )) as infos where 1=1 and infos.zone in (select zone from zones > where zones.zones=1) > group by infos.id having category_match>=2 order

Re: [sqlite] parser stack overflow in view

ag, 29. Juli 2014 um 12:54 Uhr > Von: "Richard Hipp" <d...@sqlite.org> > An: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> > Betreff: Re: [sqlite] parser stack overflow in view > > On Tue, Jul 29, 2014 at 5:00 AM, Michael <ruther1...

Re: [sqlite] parser stack overflow in view

On Tue, Jul 29, 2014 at 5:00 AM, Michael wrote: > I have a view with about 6 Unions and a depth of about 6 subselects in > each select. > Shouldn't be a big thing and it was no problem with sqlite 3.7.17. > Since 3.8 (3.8.4.3) I get "parser stack overflow". I have many

[sqlite] parser stack overflow in view

I have a view with about 6 Unions and a depth of about 6 subselects in each select. Shouldn't be a big thing and it was no problem with sqlite 3.7.17. Since 3.8 (3.8.4.3) I get "parser stack overflow". I have many queries with this problem now... Can anyone help me please Any Ideas?