Re: [sqlite] I/O error in sqlite3

I have got the reason for I/O error: It is due to PRAGMA journal mode WAL. If I run with default journal mode then application is working fine. In above case what is the system architecture requirement to get WAL mode enable? How do I can achieve better concurrency in terms of reading? Thanks.

[sqlite] I/O error in sqlite3

What is possible cause of I/O error in sqlite3? My application is running fine on Desktop PC.Same application when I try to run on ARM target it is giving I/O error. sqlite3 on Host : 3.7.9 sqlite3 on Target : 3.7.14.1 ___ sqlite-users mailing list

Re: [sqlite] Database locking Error

For read operation i am doing _prepare(), _step(), _finalize(). For all other operation i am doing _exec(). Do you see any issue ? Cheers - Techi On Mon, Aug 26, 2013 at 9:22 PM, Simon Slavin wrote: > > On 26 Aug 2013, at 9:02am, techi eth wrote: >

Re: [sqlite] Collation advice

On 8/26/2013 4:28 PM, _ph_ wrote: (btw. Muenster / Münster would fall back to full comparison due to the ü) Yes, but if you want to create a collation that sorts Muenster next to Münster, then that collation would also need to sort Muenster after, say, "mug" or "mule". -- Igor Tandetnik

Re: [sqlite] Collation advice

> In Hungarian, yes, that's what happens. I shouldn't be surprised :) I liike up digraphs (http://en.wikipedia.org/wiki/Digraph_(orthography)#Digraphs_in_Unicode) and found at least some of them have unicode code points. But if you can't cover all, yeah, normalization won't help. (btw.

Re: [sqlite] BETWEEN and explicit collation assignment

> What is relevant is not determined by the type of the object, but by > the task at hand, in other words by the comparator. No. There is only one meaning of "equal". Two things are either equal or not. How to compare them is determined by only their type. You are correct, James, types are

Re: [sqlite] Collation advice

On 8/26/2013 1:26 PM, _ph_ wrote: Should "AD" + "ZV" really compare as a "A" + "DZ" digraph +"V" in the respective language? I am not sure about the intended behavior, but it seems strange. (OTOH, language. It's always strange.) In Hungarian, yes, that's what happens. Anyway, I would

Re: [sqlite] Update field from standard input with sqlite3 command line utility

luis montes wrote: > I'm trying to do a simple database update from a bash script. It seems > to me that I should be able to do something like this from the command > line: > > cat file.xml|sqlite3 database.db 'update table1 set column3=? where > column1="some name";' Escaping arbitrary data in

Re: [sqlite] Collation advice

On 08/26/2013 11:10 PM, Jan Slodicka wrote: Thanks, Simon. As a risk, I see overriding an existing collation name as risky. If any application makes changes to the database without the extension loaded, you're going to get corrupt indexes. Can you instead make up a new collation name ? I

Re: [sqlite] BLOB & Other Data Type

You can see that e.g. with a select statement: create table test ( Name TEXT, Age Int); INSERT INTO Test VALUES ('Klaus', 22); INSERT INTO Test VALUES ('Meier', '022'); SELECT * FROM Test WHERE Age=22; In this case, the comparison is made on integers, '022' converted to integer

Re: [sqlite] Collation advice

On 26 Aug 2013, at 6:16pm, Igor Tandetnik wrote: > Furthermore, the collation depends on the system locale. If the system locale > changes, that could similarly lead to corrupted indexes. Not sure how much of > a concern that is with iOS System locale is a simple setting

Re: [sqlite] Collation advice

What Simon says extends to another case: if you change the visible behavior of that function, even if it's a necessary bug fix, you end up with broken indices. That's true for every collation sequence, though. If I interpret your code correctly, however, the user can switch the preferred

Re: [sqlite] Collation advice

FWIW: If you build a database using NOCASE version 1, then try to use the database with a different NOCASE version X where X>1, the database will appear to be corrupt, since the order of the indices will be incorrect. However, you can easily fix this by running REINDEX. That is what the REINDEX

Re: [sqlite] Collation advice

On 8/26/2013 11:44 AM, Jan Slodicka wrote: if( nKey1==nKey2 && ((UInt8*)pKey1)[0]==((UInt8*)pKey2)[0] && memcmp(pKey1,pKey2,nKey1)==0 ) return 0; There's a problem here when comparing empty strings, that is, when nKey1 == nKey2 == 0. Why are you comparing elements at index 0

Re: [sqlite] Collation advice

On 8/26/2013 11:58 AM, Simon Slavin wrote: On 26 Aug 2013, at 4:44pm, Jan Slodicka wrote: int rc = sqlite3_create_collation(db, "NOCASE", SQLITE_UTF8, 0, sqlite3_collate); As a risk, I see overriding an existing collation name as risky. If any application makes

[sqlite] SQLite port to RTOS

Hi all, I had downloaded the SQLite ver 3.8 code base from the SQLite website. In the documentation they say that it supports Unix (Linux, Mac OS-X, Android, iOS) and Windows (Win32, WinCE, WinRT). I would like to port SQLite to uITRON RTOS. Is it possible to port the code to an

Re: [sqlite] Literature on the information theory behind SQL(lite)?

I recommend this free online class from Stanford: Introduction to Databases It's pretty comprehensive (but not too in-depth) if want to get started with database theory. Here's the syllabus copied from the website: This course covers database design and the

Re: [sqlite] Collation advice

Thanks, Simon. > As a risk, I see overriding an existing collation name as risky. If any > application makes changes to the database without the extension loaded, > you're going to get corrupt indexes. Can you instead make up a new > collation name ? I did not think about this, but in our

Re: [sqlite] Collation advice

On 26 Aug 2013, at 4:44pm, Jan Slodicka wrote: >int rc = sqlite3_create_collation(db, "NOCASE", SQLITE_UTF8, 0, > sqlite3_collate); As a risk, I see overriding an existing collation name as risky. If any application makes changes to the database without the extension

Re: [sqlite] Literature on the information theory behind SQL(lite)?

O'Reilly just started a 50%-off sale on all ebooks (60% on orders of $100 or more), good through Sept. 10. A good chance to pick up these or anything else, SQL-oriented or otherwise. The discount code* *is B2S3 (but is also shown on the website). Gerry * * On Thu, Jul 18, 2013 at 5:31 AM,

Re: [sqlite] Database locking Error

On 26 Aug 2013, at 9:02am, techi eth wrote: > Fun_Read() on TblTest** > /* Do the periodic read operation by using db handler return from above*/ How is your read done ? Do you use _exec() like you do for the PRAGMA, or _prepare(), _step(), _finalize(), or _query() or

Re: [sqlite] Update field from standard input with sqlite3 command line utility

On 26 Aug 2013, at 16:14, luis montes wrote: > It seems to me that I should be able to > do something like this from the command line: > > cat file.xml|sqlite3 database.db 'update table1 set column3=? where > column1="some name";' > > That's it, I'm trying to update column 3 on a particular

[sqlite] Collation advice

Hello Please see the source code at the bottom. It represents custom NOCASE collation to be used with iOS, i.e. it is registered as int rc = sqlite3_create_collation(db, "NOCASE", SQLITE_UTF8, 0, sqlite3_collate); Main reason for this collation is the performance. It uses ascii comparison if

[sqlite] Update field from standard input with sqlite3 command line utility

I'm a SQL novice, and occasional sqlite user. I'm trying to do a simple database update from a bash script. It seems to me that I should be able to do something like this from the command line: cat file.xml|sqlite3 database.db 'update table1 set column3=? where column1="some name";' That's it,

Re: [sqlite] Path Length Limit on Windows

Hi, Richard, I myself wrote: > Von: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] > [snip] > > (2) SQLite version 3.8.0 allows for longer windows pathnames up to > >3*MAX_PATH bytes, which is 3x more space that was allowed before. > >This is still not 32K but might

Re: [sqlite] Database locking Error

> >You only have to do this once, e.g. at database creation. > >Journal mode WAL is a persistent property of the database file. > >Every connection will respect it. > All PRAGMA Option is attached to database as a persistent property? No, only the ones which are persistent. Journal_mode is

Re: [sqlite] Database locking Error

Oppps. Apologies for my mistake. My test is working correctly now. Thanks a lot. >You only have to do this once, e.g. at database creation. >Journal mode WAL is a persistent property of the database file. >Every connection will respect it. All PRAGMA Option is attached to database as a

Re: [sqlite] Database locking Error

On Mon, 26 Aug 2013 13:32:42 +0530, techi eth wrote: >PRAGMA jouranl_mode = WAL That's misspelled, both in your text and in your code. Try: PRAGMA journal_mode=WAL; You only have to do this once, e.g. at database creation. Journal mode WAL is a persistent property of the

Re: [sqlite] Database locking Error

Thanks. I tried using PRAGMA jouranl_mode = WAL but still it is getting failed for some time. Find below more details. Process 1: Fun_Open() sqlite3_open(DATABASE, ); sqlite3_exec(dbUpdate, " PRAGMA jouranl_mode = WAL", NULL, NULL, ); Fun_Update() on TblTest /* Do the periodic update

Re: [sqlite] Database locking Error

On 08/26/2013 01:37 PM, techi eth wrote: Hi, I come across database file locking error while trying below case with Update. Case: One process is updating a Colum periodically & other process is selecting same Colum or other colum in table periodically for read. What is the best way to handle

[sqlite] Database locking Error

Hi, I come across database file locking error while trying below case with Update. Case: One process is updating a Colum periodically & other process is selecting same Colum or other colum in table periodically for read. What is the best way to handle so that Update will not get locking error?