[sqlite] Sqlite incompatibility with Postgres

> It would also be very minor to add "UNION -1" as a synonym for "UNION ALL", > but "being minor" is not an argument for doing so. > While the mentorship of Postgres is undoubted, there is/was never a drive, > nor a need for full (or even partial) compatibility with "Postgres" per se, > mostly

[sqlite] Summing values by date, returning 0 for missing dates

On 2016/05/13 4:56 PM, Jonathan Moules wrote: > Hi Simon, >Sorry, maybe we're crossing wires, but I'm not sure to what you're > referring. How is defining the type as DATE impeding my attempt to get a > value of 0 for non-existent rows? > Ryan's response with a CTE seems to probably be

[sqlite] Sqlite incompatibility with Postgres

Just what I needed. Ta muchly! Regards David M Bennett FACS Andl - A New Database Language - andl.org > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of Darren Duncan > Sent: Saturday, 14

[sqlite] Time & between, midnight wrap around

Hello, BETWEEN doesn't give the result I would need when used with time before & after midnight: SELECT time('23:00') BETWEEN time('22:00') AND time ('23:30'); time 1 sqlite> SELECT time('23:00') BETWEEN time('22:00') AND time ('01:00'); time 0 Any suggestion how to tweak the query

[sqlite] Sqlite incompatibility with Postgres

On Fri, 13 May 2016 15:13:01 +0100 Simon Slavin wrote: > On 13 May 2016, at 3:07pm, dandl wrote: > > > I have no deep knowledge of standard SQL. > > I used to know SQL92 very well. There's no facility for doing > anything like LIMIT or OFFSET in it. You had to use your programming >

[sqlite] 64bit DLL vs 32bit

On Wed, 11 May 2016 11:30:34 +1000 "dandl" wrote: > > more about DLLs than it is about SQLite. > > Actually, it's everyone using a language other than C/C++, plus a > proportion of those too. I use C#, but if you want to call Sqlite > from Java, Python, etc or even some generic C/C++ app that

[sqlite] Time & between, midnight wrap around

On 2016/05/14 8:28 PM, Daniel Polski wrote: > Hello, > BETWEEN doesn't give the result I would need when used with time > before & after midnight: > > SELECT time('23:00') BETWEEN time('22:00') AND time ('23:30'); > time > > 1 > > sqlite> SELECT time('23:00') BETWEEN time('22:00') AND time

[sqlite] Podcast with Dr Hipp: SQLite history, success and funding

Those interested in SQLite might like to listen to Play on the page or download as an MP3. Unusual information on Dr Hipp's early career, SQLite history, HWACI, and how come SQLite is free but the developers still manage to afford food and somewhere to sleep.

[sqlite] 64bit DLL vs 32bit

On Thu, 12 May 2016 00:36:31 +1000 "dandl" wrote: > But I think if you compile code for the x64 processor chip and call > it from x86 or vice versa then either it doesn't work or you pay a > high price for thunking from one to the other. I think that's > unavoidable regardless of OS. Right:

[sqlite] Podcast with Dr Hipp: SQLite history, success and funding

thanks for letting us know about that, thoroughly enjoyed listening?. On May 14, 2016, at 2:17 PM, Simon Slavin wrote: > Those interested in SQLite might like to listen to > > > > Play on the page or download as an MP3. > > Unusual information on Dr Hipp's early

[sqlite] Podcast with Dr Hipp: SQLite history, success and funding

Just finished listening to it as well. Dr Hipp, I know you don't like to toot your own horn, but, really, I'd really like to hear where and when you're talking to other people about SQLite and your other projects. Really interesting info. On Sat, May 14, 2016 at 5:49 PM, Steve Schow wrote: >

[sqlite] Sqlite incompatibility with Postgres

On 2016-05-14 11:30 AM, James K. Lowden wrote: > I suggest the reason LIMIT hasn't been standardized is that it's > contrary to the fundamental idea that rows in a table have no > meaningful order. SQL doesn't honor relational theory with complete > fidelity, but at least that horse is still in

[sqlite] Sqlite incompatibility with Postgres

Someone should wake the SQL standard committee and nominate sqlite being the broadest used so should fill some gaps in specification with it. :) and conversely blame the others for their incompatibility :)