Re: [sqlite] Concrete example of corruption

> D. Richard Hipp wrote: > Please try the changes in the branch at > http://www.sqlite.org/src/info/8759a8e4d8 and > let me know if they adequately cover your concerns. I don't have enough expertise with the SQLite codebase to be able to tell for sure. You will always know better than me

[sqlite] A read right after a write does not read changes

I'm using Entity Framework to access my SQLite database and I wrote a routine today that edits an existing table record. Then in the same program (step 2), I use the key that I just used to modify the record and I create a new instance of the same table and read the record that I just modified,

Re: [sqlite] Vacuum command in a transaction?

On 2013/12/11 01:41, veeresh kumar wrote: Thanks Igor and Simon for your inputs. I was under the impression that VACUUM would also help performance since it does defragmentation. Hi Veeresh, Vacuum does de-fragment the database, it also amalgamates any transaction files and so on - so you

Re: [sqlite] Vacuum command in a transaction?

Thanks Igor and Simon for your inputs. I was under the impression that VACUUM would also help performance since it does defragmentation. On Tuesday, 10 December 2013 3:02 PM, Simon Slavin wrote: On 10 Dec 2013, at 8:04pm, veeresh kumar wrote: >

Re: [sqlite] Vacuum command in a transaction?

On 10 Dec 2013, at 8:04pm, veeresh kumar wrote: > -If we put inside a transaction, definitely we would get a SQLITE_BUSY > error.Any way to avoid this error? It is normal for SQL engines to prevent VACUUM inside a transaction, and to lock the database from other

Re: [sqlite] Vacuum command in a transaction?

On 12/10/2013 3:04 PM, veeresh kumar wrote: I wanted to know what is the good way to execute Vacuum command. - Inside a transaction or without transaction? Doesn't really matter (unless you want to combine it with other statements in a single transaction). VACUUM command is no different

[sqlite] Vacuum command in a transaction?

The database size that we use in the application can grow upto 50 GB. We have an option of shrinking the database using the Vacuum command. I understand that Vacuum command consumes lots of time to execute,but i dont see any other way. I wanted to know what is the good way to execute Vacuum

Re: [sqlite] [BUG; 3.7.13] ANALYZE leads to a wrong query plan for RTrees

Am 10.12.2013 um 10:59 schrieb Dan Kennedy : > On 12/10/2013 02:44 PM, skywind mailing lists wrote: >> This is an example that the ANALYZE command leads to a wrong query plan for >> RTrees: >> >> CREATE TABLE A (ID INTEGER PRIMARY KEY, Latitude, Longitude, Altitude); >>

Re: [sqlite] sqlite does not order greek characters correctly

"Simon Slavin" wrote... On 10 Dec 2013, at 4:23pm, jose isaias cabrera wrote: "Simon Slavin" wrote... If you're not already using it, please take a look at the International Components for Unicode:

Re: [sqlite] sqlite does not order greek characters correctly

On 10 Dec 2013, at 4:23pm, jose isaias cabrera wrote: > "Simon Slavin" wrote... > >> If you're not already using it, please take a look at the International >> Components for Unicode: >> >> > > Hi Simon.

Re: [sqlite] sqlite does not order greek characters correctly

"Simon Slavin" wrote... On 8 Dec 2013, at 9:34pm, Nikos Platis wrote: I tried to order a table by a column containing greek strings and I found out that sqlite does not sort them correctly. It probably uses the order of greek characters in the Unicode table, while the

Re: [sqlite] sqlite does not order greek characters correctly

On Sun, 8 Dec 2013 21:53:51 +, Simon Slavin wrote: > > If you're not already using it, please take a look at the International > Components for Unicode: > > > > It's a compilation option. > > Simon.

Re: [sqlite] [BUG; 3.7.13] ANALYZE leads to a wrong query plan for RTrees

On 12/10/2013 02:44 PM, skywind mailing lists wrote: This is an example that the ANALYZE command leads to a wrong query plan for RTrees: CREATE TABLE A (ID INTEGER PRIMARY KEY, Latitude, Longitude, Altitude); CREATE VIRTUAL TABLE B USING RTree (ID, FromLatitude, TillLatitude,

[sqlite] duplicate table aliases

Hi List, By coincidence we discovered that SQLite allows to use the same tables aliases multiple times in one query at the same level. As long as all referred columns are unambiguously named SQLite does not complain about duplicate table aliases. Although I cannot find any documentation that