[sqlite] Fix for non unix times DATETIME

On 10 Jul 2015, at 6:12pm, Lee Reiber wrote: > Searching for many days on a fix to the dreaded DATETIME mapping to .NET. My guess is that this is a reference to Simon.

[sqlite] Suggestions for Fast Set Logic?

On 10 Jul 2015, at 5:58pm, James K. Lowden wrote: > Simon Slavin wrote: > >> If you're going to do it properly you have a keywords column which >> contains strings like >> >> , >> ,animal, >> ,animal,predator, >> ,animal,predator,bird, > > Why do it that way? I would recommend a schema like

[sqlite] Fix for non unix times DATETIME

More to the first post than the second yes On Fri, Jul 10, 2015, 11:32 AM Simon Slavin wrote: > > On 10 Jul 2015, at 6:12pm, Lee Reiber wrote: > > > Searching for many days on a fix to the dreaded DATETIME mapping to .NET. > > My guess is that this is a reference to > >

[sqlite] Fix for non unix times DATETIME

Searching for many days on a fix to the dreaded DATETIME mapping to .NET. Of course SQLite technically does not have a datetime per-say as I clearly understand but the problem remains with dates such as Mac absolute and also Java datetimes. The fun "string cannot be converted to string" is what I

[sqlite] System.Data.Sqlite3.dll for OSX

Sorry if this has been asked many times before. I have having great difficulty finding a copy of the .NET (mono) assembly System.Data.Sqlite3.dll for OS X. None I have tried work, and the Xamarin Studio can?t compile the C++ needed to build my own. Tried many libs, none of seems to work. Afte

[sqlite] System.Data.Sqlite3.dll for OSX

Ben Clewett wrote: > > I have having great difficulty finding a copy of the .NET (mono) assembly > System.Data.Sqlite3.dll for OS X. None I have tried work, and the Xamarin > Studio can't compile the C++ needed to build my own. > Are you able to compile managed binaries on Windows? h

[sqlite] Suggestions for Fast Set Logic?

On 10 Jul 2015, at 4:14pm, Andy Rahn wrote: > I don't think > there is a way I can just concatenate an extensive list of WHERE clauses > into one monolithic SQLite query and also guarantee that SQLite will be > able to SEARCH via indexes instead of falling back to slow SCANS. You are engaged in

[sqlite] Fix for non unix times DATETIME

Lee Reiber wrote: > > Is there a way on connection to use a flag to GetAllAsTextIfDateTime ? > The following might be able to help: SQLiteConnection connection = new SQLiteConnection( "Data Source=C:\\some\\path\\test.db;Flags=UseConnectionTypes;"); connection.AddTypeMapping("DATETIME", DbT

[sqlite] busy_timeout() not working always?

Thanks for you reply Keith, On Fri, Jul 10, 2015 at 1:30 AM, Keith Medcalf wrote: > > Turn off shared-cache mode. > > Shared-cache is designed for use on itty-bitty-tiny computers with only a > few KB of RAM and very paltry CPU resources. On equipment for which shared > cache was designed, you

[sqlite] Suggestions for Fast Set Logic?

On Thu, 9 Jul 2015 22:28:04 +0100 Simon Slavin wrote: > If you're going to do it properly you have a keywords column which > contains strings like > > , > ,animal, > ,animal,predator, > ,animal,predator,bird, Why do it that way? I would recommend a schema like Keith's, with one keyword per row

[sqlite] Regarding Result Set

Sir, I created a custom Result set in Resultrow case in sqlite3VdbeExec function as below custom_pResultSet = (Mem*) malloc(sizeof (Mem) * (custom_numElements)); and I initialized it using sqlite3VdbeMemInit function. for( i = 0 ; i < custom_numElements ; i++ )

[sqlite] Suggestions for Fast Set Logic?

Thanks for the suggestions. Keith, Igor and Simon, I will definitely look at your SQL examples and compare them to my implementation! But, I admit I feel guilty for not adequately explaining the problem I'm trying to solve in its entirety. For one thing, I'm in a very performance sensitive situa

[sqlite] Suggestions for Fast Set Logic?

While I am opposed to premature optimization as well, this is not clearly a case of that. As described, the user will be able to create arbitrarily complex queries. Since it is impossible to know in advance what indexes might be required, breaking it down to individual sub queries with simple where