Re: [sqlite] Upgrading SQLite versions
Very weird... I thought so they would be compatible. But when I delete the old database and restart the program it works fine... (recreation of a new database with the new version)... Nothing else has changed except the sqlite-version (2.8.13->2.8.15). I work with UTF8 1 and ISO8991 0 (or something like that). The two ways I have tried it are: 1/ same box, same program, 2 accounts (via winxp fast user switching)... The 1st one opens the program, the second one opens the program and tries to insert a new adress. No constant polling of the database is done etc?? 2/ 2 computers, common share on windows server... 1 person opens the program on 1 client, 2nd person on 2nd client, 2nd tries to insert an adress... Both setups give 'database is locked'. :S Sorry for the long delay (no internet for 4 days -> arrgh). At 10:15 20/08/2004, you wrote: Steven Van Ingelgem wrote: Hi, 1/ I am currently using 2.8.13 and I wanted to upgrade it to 2.8.15... Now when I do that, my program crashes when I try to open (sqlite_open) the database on the following function: rc = sqliteBtreeFactory(db, zFilename, 0, MAX_PAGES, >aDb[0].pBt); Is that "normal" behaviour (for instance: no binary compatibilities between 2.8.x versions?). Of course that would be better then to immediatly upgrade to 3.0 if i have to convert all the databases ofcourse. But then the same question stays... Is there compatibility between those versions? (again I mean: just update the source & I can still work on the same databases without doing something special). 2/ I use wxSQLite to access databases. When 1 person has my program open (just open, that means not doing anything). Then another person opens a program from a different location, and access the same databases. He can read it without a problem, but he can't do any insert/update/delete ? (so I think he can acquire readlock, but no writelock). [using 2.8.13]. Is this a feature or a bug? (as far as I understood, sqlite locks the database file when it is needed, but not all the time?). Could someone answer those questions, I would be very gratefull. BTW, if I am unclear somewhere, please request more information! Thx, KaReL (aka Steven) *Main Webpage* : http://www.karels0ft.be/ *ICQ #* : 35217584Sqlite minor versions should have compatible database formats, so if you're having crashes, there's probably a problem somewhere else. For the other question, how are the two people accessing the database file? NFS, samba, or just different terminals on the same box? This can make a difference, as locking on network filesystems has varying levels of success(although it is never reccomended). John LeSueur KaReL (aka Steven) Main Webpage : http://www.karels0ft.be/ ICQ # : 35217584
Re: [sqlite] Upgrading SQLite versions
Steven Van Ingelgem wrote: Hi, 1/ I am currently using 2.8.13 and I wanted to upgrade it to 2.8.15... Now when I do that, my program crashes when I try to open (sqlite_open) the database on the following function: rc = sqliteBtreeFactory(db, zFilename, 0, MAX_PAGES, >aDb[0].pBt); Is that "normal" behaviour (for instance: no binary compatibilities between 2.8.x versions?). Of course that would be better then to immediatly upgrade to 3.0 if i have to convert all the databases ofcourse. But then the same question stays... Is there compatibility between those versions? (again I mean: just update the source & I can still work on the same databases without doing something special). 2/ I use wxSQLite to access databases. When 1 person has my program open (just open, that means not doing anything). Then another person opens a program from a different location, and access the same databases. He can read it without a problem, but he can't do any insert/update/delete ? (so I think he can acquire readlock, but no writelock). [using 2.8.13]. Is this a feature or a bug? (as far as I understood, sqlite locks the database file when it is needed, but not all the time?). Could someone answer those questions, I would be very gratefull. BTW, if I am unclear somewhere, please request more information! Thx, KaReL (aka Steven) *Main Webpage* : http://www.karels0ft.be/ *ICQ #*: 35217584 Sqlite minor versions should have compatible database formats, so if you're having crashes, there's probably a problem somewhere else. For the other question, how are the two people accessing the database file? NFS, samba, or just different terminals on the same box? This can make a difference, as locking on network filesystems has varying levels of success(although it is never reccomended). John LeSueur
[sqlite] Upgrading SQLite versions
Hi, 1/ I am currently using 2.8.13 and I wanted to upgrade it to 2.8.15... Now when I do that, my program crashes when I try to open (sqlite_open) the database on the following function: rc = sqliteBtreeFactory(db, zFilename, 0, MAX_PAGES, >aDb[0].pBt); Is that "normal" behaviour (for instance: no binary compatibilities between 2.8.x versions?). Of course that would be better then to immediatly upgrade to 3.0 if i have to convert all the databases ofcourse. But then the same question stays... Is there compatibility between those versions? (again I mean: just update the source & I can still work on the same databases without doing something special). 2/ I use wxSQLite to access databases. When 1 person has my program open (just open, that means not doing anything). Then another person opens a program from a different location, and access the same databases. He can read it without a problem, but he can't do any insert/update/delete ? (so I think he can acquire readlock, but no writelock). [using 2.8.13]. Is this a feature or a bug? (as far as I understood, sqlite locks the database file when it is needed, but not all the time?). Could someone answer those questions, I would be very gratefull. BTW, if I am unclear somewhere, please request more information! Thx, KaReL (aka Steven) Main Webpage : http://www.karels0ft.be/ ICQ # : 35217584
