Closed kerel-fs closed 8 years ago
I cannot reproduce it, but I am using postgresql. Where does the '\n' in the sql statement comes from? I will have a closer look.
I can confirm that there are no issues with a postresql- backend and found the problem: SQLite lacks support of analytic functions (LAG here), thus both commands don't work with a sqlite-backend.
We should state that logbook requires a postgresql- backend in the README but continue to use sqlite preconfigured because of its simplicity.
Or is it easily possible to rewrite those queries to support sqlite?
Lag and lead make the calculation very fast. But I will look after a solution so we keep SQLite compatibility.
related: ae3b08722f0acd761148138ebc0c7ba773a06d07 README: Add note about special backend requirements for some tasks
Added a recommendation for postgresql-backend to README.
Since we need PostGIS there is no chance anymore for SQLite
and
@Meisterschueler any ideas?