Re: [sqlite] [EXTERNAL] Window functions

t; -Ursprüngliche Nachricht- > Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > Im Auftrag von Shevek > Gesendet: Donnerstag, 26. April 2018 10:36 > An: SQLite mailing list > Betreff: Re: [sqlite] [EXTERNAL] Window functions > > About s

Re: [sqlite] [EXTERNAL] Window functions

supported from then on to eternity. -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Shevek Gesendet: Donnerstag, 26. April 2018 10:36 An: SQLite mailing list Betreff: Re: [sqlite] [EXTERNAL] Window functions About storing

Re: [sqlite] [EXTERNAL] Window functions

About storing the whole result set: Note that in postgresql-derivatives (and Oracle? maybe Teradata?), this is valid: select lag(a0, a0) over () from a; whereas many other servers (which I won't name) require the second argument of lag() to be constant. If it is constant (even in postgresql-d

Re: [sqlite] [EXTERNAL] Window functions

"Window functions" aka "scrollable cursors" require that the whole result set ist stored somewhere. Or at least the current position of all of the tables/indices involved in producing it, provided that such positions are settable. You then need to keep track of how many records need to be produc