Re: [sqlite] Min/Max and skip-scan optimizations

2019-01-27 Thread Keith Medcalf
Do you perhaps want this: select source1, source2, ( select min(ts) from rolling where source1 = x.source1 and source2 = x.source2 ) from ( select distinct source1, source2 from rolling

[sqlite] Min/Max and skip-scan optimizations

2019-01-27 Thread Gerlando Falauto
Hi, I have a database table looking like this: CREATE TABLE `rolling` ( `source1`TEXT NOT NULL, `source2`TEXT NOT NULL, `ts`INTEGER NOT NULL, `value`TEXT ); CREATE INDEX `sources` ON `rolling` ( `source1`, `source2`, `ts` ); INSERT INTO rolling WI

Re: [sqlite] Support for System.Data.SQLite: Different API type for int/integer columns

2019-01-27 Thread Joe Mistachkin
JP wrote: > > The answers don't explain why there is a bitness difference at run-time > between the types retrieved from INT and INTEGER columns, and that's my > question. From reading https://sqlite.org/datatype3.html I understand > there should be no difference whatsoever between defining a colu

Re: [sqlite] Support for System.Data.SQLite: Different API type for int/integer columns

2019-01-27 Thread Simon Slavin
On 24 Jan 2019, at 3:27pm, JP wrote: > I have encountered the same problem as this: > https://stackoverflow.com/q/4925084 What is returned by typeof(reader["myColumn"]) in each case ? I suspect that you're getting an integer when the column is declared as INTEGER, but not when the column is d

[sqlite] Support for System.Data.SQLite: Different API type for int/integer columns

2019-01-27 Thread JP
Hello, I have encountered the same problem as this: https://stackoverflow.com/q/4925084 The answers don't explain why there is a bitness difference at run-time between the types retrieved from INT and INTEGER columns, and that's my question. From reading https://sqlite.org/datatype3.html I unde