Re: [sqlite] How to verify referential integrity of SQLite database

A way to verify the constraint integrety would be great. Some thoughts: - Introduce a boolean 'all_foreign_key_constraits_are_known_valid' (default false) that is stored in the database header - A new PRAGMA foreign_key_check checks the foreign key constraints - If it finds invalid constraints an

Re: [sqlite] How to verify referential integrity of SQLite database

> This seems like a reasonable request. And while we are at > it, we will likely also verify UNIQUE and CHECK constraints too. > > PRAGMA quick_check is still available for users who do not > want to take the extra overhead of verifying UNIQUE, CHECK, > and foreign key constraints. > > Does

Re: [sqlite] Why can't sqlite disregard unused outer joins?

> Actually, anytime you have VIEWs that join table sources you > can benefit from this optimization. No, there is only a benefit if the optimization actually finds a table that can be removed from the join. If in (my opinion) 99.99% of the queries no such table can or will be found, the optimiza

[sqlite] Implement autocomplete with fts4aux

With fts4aux, the term table would be a perfect candidate to implement an autocomplete function in our application. However a query SELECT term FROM ft_terms WHERE term LIKE 'descr%' is quite slow as no 'index' is used (indexes are not possible on virtual tables). With checkin

[sqlite] FTS simple tokenizer with custom delimeters

While looking around in the source of the simple tokenizer I found code that suggests custom delimeters can be specified (I want to exclude the underscore). http://www.sqlite.org/src/artifact/5c98225a53705e5ee34824087478cf477bdb7004? ln=76-87 An indeed: CREATE VIRTUAL TABLE ft USING fts

Re: [sqlite] SQLite 3.7.11 behavioral change from 3.7.10 with concurrency -- bug??

>From the docs: 'The default isolation level for SQLite is SERIALIZABLE' As far as I understand this means: you will not see changes made by other connections (committed or uncommited) after your transaction started. If another connections commits a change, you will not see it. I would expect: If

Re: [sqlite] rtree value rounding

l 2012 17:52 > To: General Discussion of SQLite Database > Subject: Re: [sqlite] rtree value rounding > > On Tue, Apr 24, 2012 at 11:41 AM, Jos Groot Lipman > wrote: > > > The next version of Sqlite will very likely support 64 bit > integers as > > RTree val

Re: [sqlite] rtree value rounding

The next version of Sqlite will very likely support 64 bit integers as RTree values. Would that solve your problems? http://www.sqlite.org/src/info/02b7640f51 -- Jos Groot Lipman > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlit

Re: [sqlite] Side-by-side with checked out content

Sorry, wrong group. Reposted in the Fossil group ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Side-by-side with checked out content

Is it possible to see a side-by-side difference between the last checkin and the currently changed file on disk? It would be a great alternative to fossil diff and fossil gdiff This would be much like the wiki preview using /doc/ckout/ -- Jos Groot Lipman

Re: [sqlite] sqlite3.dll version information not available

Using the sqlite3_libversion is different, it can only be used *after* the DLL has been loaded. With Thomas' solution he can check the version without/before loading the DLL -- Jos Groot Lipman > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sql

Re: [sqlite] FTS simple tokenizer

It was reported before (and not solved) http://www.mail-archive.com/sqlite-users@sqlite.org/msg55959.html > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Hamish Allan > Sent: maandag 27 februari 2012 11:27 > To: General

Re: [sqlite] /**** ERROR: (11) database disk image is malformed *****/

hat has not been synced, data is written at offset 0 which should not have been written there. (The total size of the cortupt file seems more or less correct) -- Jos Groot Lipman ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080

Re: [sqlite] /**** ERROR: (11) database disk image is malformed *****/

the problem no matter how hard I try. -- Jos Groot Lipman -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Folkert van Heusden Sent: woensdag 4 januari 2012 15:21 To: sqlite-users@sqlite.org Subject: [sqlite] / ERROR:

Re: [sqlite] Cache design using sqlite3...

sparent to the readers. How would they see the new data? On Tue, Dec 6, 2011 at 5:23 PM, Jos Groot Lipman wrote: > > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Alejandro > Martínez > Sent: dinsda

Re: [sqlite] Cache design using sqlite3...

-Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Alejandro Martínez Sent: dinsdag 6 december 2011 19:35 To: General Discussion of SQLite Database Subject: [sqlite] Cache design using sqlite3... I'm trying to use sqlite3 as a ca

Re: [sqlite] FW: How about a proper forum rather than an e-mail list

> Yes, go install your forum and leave us in peace :P Who said mail-lists get less flame-wars ;-) ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Limit COUNT

SELECT COUNT(*) FROM table will always return exactly 1 record (with the count). LIMIT 5000 limits the number of records returned to 5000. As 1 record < 5000 records the 5000 is effecively ignored -- Jos -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun.

Re: [sqlite] How to register on the wiki

Cecil, I think nobody 'gave' you the code because it does not exists. There is no simple standard set of statements to execute for a speed comparison. If it were that simple somebody would have retested it long ago. Doing a fair comparion also involves all sort of configuraton comparions. For exa

Re: [sqlite] Three questions

> We're not saying there no place for '*', merely that it shouldn't be used unless you actually want '*'. And suppose there is very_large_blob_field you don't need right now. If you do a 'select *' it will be read from disk unnecessary even if you are not going to use it. That is reason enough to

Re: [sqlite] BUG : round(x,y) not consistent

The rounding problem is documented in the FAQ: http://www.sqlite.org/faq.html#q16 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Order of UNION query results

The result without an order by clause is always undefined. It might be ordered to your liking in the current version and be different in the next version. Never rely on an ordering without an order by clause. Use this instead: select coalesce(po.value, pp.value) from params pp where key='setti

[sqlite] FTS3 simple tokenizer splits at underscore

The documentation at http://www.sqlite.org/fts3.html#tokenizer states about the tokenizer eligible characters are all alphanumeric characters, the "_" character, and all characters with UTF codepoints greater than or equal to 128 This suggests to me that an underscore is part of wo