Re: [sqlite] [sqlite-dev] Implementing per-value custom types

On 2014-11-26, 7:53 AM, RSmith wrote: > The fact that inside of SQLite an Integer can be stored in different > ways is simply a code/data/space optimisation for SQLite, it is > transparent to the user and transparent to the SQL - it is in no way > intended as a data-feature or extension of the SQL

Re: [sqlite] Serializing an object's vector or array using sqlite3 in c++

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2014-11-21, 12:52 AM, Thane Michael wrote: > I've been searching for a way to serialize an object's vector using > sqlite3 but are yet find a working solution. How do I go about > making it happen, an example would be of great help. If your goal

Re: [sqlite] Database is locked exceptions

On 2014-10-29, 12:13 PM, Mike McWhinney wrote: System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at

Re: [sqlite] Full text search: Regression on 3.8.7 (or using incorrectly?)

On 2014-10-09, 11:09 AM, Dan Kennedy wrote: On 10/09/2014 07:23 PM, Sohail Somani wrote: On 2014-10-09, 7:32 AM, Dan Kennedy wrote: Got it, thanks for the explanation. Just to make sure that I understand you correctly, is the clause MATCH '*l0l* *h4x*' getting translated to MATCH 'l0l* h4x

Re: [sqlite] Full text search: Regression on 3.8.7 (or using incorrectly?)

On 2014-10-09, 7:32 AM, Dan Kennedy wrote: Got it, thanks for the explanation. Just to make sure that I understand you correctly, is the clause MATCH '*l0l* *h4x*' getting translated to MATCH 'l0l* h4x*'? Yes, that's right. Dan. In that case, shouldn't the test in the original post have

Re: [sqlite] Full text search: Regression on 3.8.7 (or using incorrectly?)

On 2014-10-07, 4:04 PM, Dan Kennedy wrote: On 10/08/2014 01:52 AM, Sohail Somani wrote: Figured it out: match terms should be "l0l* h4x*" NOT "*l0l* *h4x*", though it did work as expected with the older version. I'd suggest keeping the old behaviour unless there is a perf

Re: [sqlite] Full text search: Regression on 3.8.7 (or using incorrectly?)

Figured it out: match terms should be "l0l* h4x*" NOT "*l0l* *h4x*", though it did work as expected with the older version. I'd suggest keeping the old behaviour unless there is a performance-based reason not to. On 2014-10-07, 2:49 PM, Sohail Somani wrote: SELECT COUNT

[sqlite] Full text search: Regression on 3.8.7 (or using incorrectly?)

$ ./bin/sqlite3 --version 3.7.17 2013-05-20 00:56:22 118a3b35693b134d56ebd780123b7fd6f1497668 $ ./bin/sqlite3 -batch < /tmp/test.sql --- 1 --- 0 --- 2 --- 1 $ ./bin/sqlite3 --version 3.8.7 2014-09-30 19:04:41 5ce05757aac80b99c3b2141cd301809f8e28e661 /bin/sqlite3 -batch < /tmp/test.sql --- 1

Re: [sqlite] Can't figure out how to report a bug

On 2014-09-07, 8:26 AM, Joe Mucchiello wrote: PmaReader *pReadr; SortSubtask *pLast = >aTask[pSorter->nTask-1]; rc = vdbeSortAllocUnpacked(pLast); if( rc==SQLITE_OK ){ pReadr = (PmaReader*)sqlite3DbMallocZero(db, sizeof(PmaReader)); pSorter->pReader

Re: [sqlite] Handling Timezones

On 2014-07-29, 8:23 PM, Will Fong wrote: Hi, On Wed, Jul 30, 2014 at 8:16 AM, Igor Tandetnik wrote: 'localtime' and 'utc' modifiers. Ah! I have not explained my issue properly :) I'm very sorry about that. I'm using SQLite as a backend to a small website and I have

Re: [sqlite] Data visibility problem

On 22/06/2014 6:33 PM, João Ramos wrote: The issue appeared with the following scenario: - using SQLite v3.8.4.3 - the DB is in WAL mode and running with multi-thread mode - every thread has a read-only DB connection (using thread-local-storage) - a single DB connection is shared between threads

Re: [sqlite] Any way to debug which query/connection is holding a share lock?

On 13/06/2014 4:38 PM, RSmith wrote: If none of these finds you a culprit, it means your program is the only thing left to blame. Here we need to start with logging every time you create a connection and start a query or creating a prepared statement. Log the handles or object IDs you get back

Re: [sqlite] Any way to debug which query/connection is holding a share lock?

On 13/06/2014 11:04 AM, RSmith wrote: On 2014/06/13 15:02, Sohail Somani wrote: My application's architecture looks roughly like this: - A main thread which does only database reads - A dedicated database write thread I needed to create this because while reads are fast, there are occasions

[sqlite] Any way to debug which query/connection is holding a share lock?

Hi, My application's architecture looks roughly like this: - A main thread which does only database reads - A dedicated database write thread I needed to create this because while reads are fast, there are occasions where writes take a significant portion of time and that can cause the main