[sqlite] Sqlite fd problem!

you are probably missing to finalize the statement prior calling sqlite3_close(). additionally you may check the return value of sqlite3_close() - it will tell you something. marcus Am 16.11.2015 um 12:02 schrieb Nader Lavasani: > Hi all, > > This happened in iOS with Objective-C language. > >

[sqlite] ATTACH DATABASE statement speed

Just another guess: Have you tried to increase the page chache drastically ? I can remeber that "PRAGMA quick_check" is pretty slow for bigger DBs without an increased page cache. Maybe something like: PRAGMA cache_size=50; PRAGMA quick_check; Marcus Am 18.08.2015 um 12:38 schrieb Paolo

[sqlite] Appropriate Uses For SQLite

We use sqlite as the db engine inside a server application with a number of clients that connect to the server. Sqlite works just beatiful here and I wish these statements "sqlite shall not be used for client/server things" would be worded less generally. In fact when we mention sqlite as our db

Re: [sqlite] Bug in sqlite.exe?

Am 2013-11-30 20:04, schrieb Eric Teutsch: Sorry, should have pointed out that the "missing" tables are: CollectionDevices and CollectionChannels You have the DB file in ProgramData, maybe you are a victim of the windows file virtualization ? Try to use a different folder and see if that

Re: [sqlite] how to move around records in sqlite as the way as in CDaoRecordset of MFC??

e.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Marcus Grimm MedCom GmbH Darmstadt, Rundeturmstr. 12, 64283 Darmstadt Tel: +49(0)6151-95147-10 Fax: +49(0)6151-95147-20 web: www.me

Re: [sqlite] CREATE INDEX on huge DB fails with SQLITE_NOMEM

On 09.10.2012 12:46, Clemens Ladisch wrote: Marcus Grimm wrote: I can see that the application increases memory up to appx. 600 MB while the database is populated - That is the cache_size=50, I assume. cache_size=50 corresponds to: 255 MB (page size 512 bytes) 488 MB (page size 1

Re: [sqlite] CREATE INDEX on huge DB fails with SQLITE_NOMEM

On 09.10.2012 11:00, Marcus Grimm wrote: On 09.10.2012 10:44, Dan Kennedy wrote: On 10/09/2012 03:30 PM, Marcus Grimm wrote: Hello, I'm currently investigating how far I can go with my favorite DB engine. For that purpose I'm testing my application with an artificial database that is appx. 50

Re: [sqlite] CREATE INDEX on huge DB fails with SQLITE_NOMEM

On 09.10.2012 10:44, Dan Kennedy wrote: On 10/09/2012 03:30 PM, Marcus Grimm wrote: Hello, I'm currently investigating how far I can go with my favorite DB engine. For that purpose I'm testing my application with an artificial database that is appx. 50 times bigger that the maximum I have seen

[sqlite] CREATE INDEX on huge DB fails with SQLITE_NOMEM

Hello, I'm currently investigating how far I can go with my favorite DB engine. For that purpose I'm testing my application with an artificial database that is appx. 50 times bigger that the maximum I have seen in the field so far. The test creates a database from the scratch and just fills the

Re: [sqlite] C++ - WHERE clause - 2nd update

On 07.09.2012 08:58, Arbol One wrote: I got this code to work, however, I am getting a segmentation fault on this code. I pass to SQLite only one statement [db->setStmt(apstr);], I read the first of the 'fname', but I don't know how to get to the second 'fname' in the database. I am not very

Re: [sqlite] sqlite3_trace() threadsafe

Am 2012-09-05 18:53, schrieb esum: Thank you so much for all help. I really appreciate it. /"All the same, I'm guessing that http://www.sqlite.org/src/info/39f763bfc0will fix your problem."/ I gave this new src code from the src tree a shot, but I seem to be getting the same behavior.

Re: [sqlite] using the SQLITE_BUSY and BEGIN IMMEDIATE

Am 2012-07-10 20:50, schrieb deltagam...@gmx.net: In http://ideone.com/eWPWD is my example code. I would like to know if this would be an appropiate implemetation/use of BEGIN IMMEDIATE and sqlite3_busy_timeout. sqlite3_busy_timeout is specified once per db connection. Probably at the

Re: [sqlite] An interesting (strange) issue with selects [solved]

Am 2012-06-30 12:06, schrieb Dennis Volodomanov: On 30/06/2012 7:47 PM, Marcus Grimm wrote: Here is another theory: Maybe you run into an issue with Windows 7 Virtualization, I did run into a similar effect with the registry access/write sometime go - mainly with Windows 7 Home Editions

Re: [sqlite] An interesting (strange) issue with selects

Here is another theory: Maybe you run into an issue with Windows 7 Virtualization, I did run into a similar effect with the registry access/write sometime go - mainly with Windows 7 Home Editions, by reading this: http://support.microsoft.com/kb/927387/EN-US It suggests that something similar

Re: [sqlite] An interesting (strange) issue with selects

lite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Marcus Grimm MedCom GmbH Darmstadt, Rundeturmstr. 12, 64283 Darmstadt Tel: +49(0)6151-95147-10 Fax: +49(0)6151-95147-20 web: www.medcom

Re: [sqlite] Problem with select

On 20.06.2012 15:03, deltagam...@gmx.net wrote: Hello, I have a problem with the selection of the row, errorcode 21 s You are missing a sqlite3_prepare_v2 for your select. Indeed I would like to retrieve all rows, but as far as I understand it, this construction will retrieve only the

Re: [sqlite] Using "attach database" to work around DB locking

> Converting variable name to variable ID (with separate lookup table) > was one of my first ideas, but turns out that the lookup itself was a > bigger hit in performance than the indexing. I'll revisit that and > see if I failed to tweak something properly. To me it sounds that it will just

Re: [sqlite] Backup API handling of corrupt source DB

>>> You can do the backup and after that do an integrity check on the >>> backup. Surely you're backing up on a different >>> server, don't you? If the back up pass the integrity check it a real >>> backup, if not, launch a warning. >> >> Yeah, that's a good idea. >> Ohh boy, why I didn't think

Re: [sqlite] Backup API handling of corrupt source DB

On 07.03.2012 13:13, Eduardo Morras wrote: At 12:22 07/03/2012, you wrote: Dear list, I'm using the backup api to frequently backup a running sqlite database. I'm wondering if the backup API is able to detect a corrupt database or will it simply also backup a corrupt DB ? I evaluating the

Re: [sqlite] Backup API handling of corrupt source DB

On 07.03.2012 12:53, Simon Slavin wrote: On 7 Mar 2012, at 11:22am, Marcus Grimm<mgr...@medcom-online.de> wrote: I evaluating the need to issue a (timeconsuming) "pragma integrity_check" prior running the backup to avoid that a backup will be overwritten with an invalid dat

[sqlite] Backup API handling of corrupt source DB

Dear list, I'm using the backup api to frequently backup a running sqlite database. I'm wondering if the backup API is able to detect a corrupt database or will it simply also backup a corrupt DB ? I evaluating the need to issue a (timeconsuming) "pragma integrity_check" prior running the

Re: [sqlite] sqlite3_step getting core dumbed.

) is sqlite3_step(stmt); really required here ? what is the result of step ? is it SQLITE_ROW ? If not, probably sqlite3_column_type doesn't make much sense. Marcus Marcus Grimm wrote: try changing this: colNames = (char **)malloc(sizeof(char)); into something like colNames = (char

Re: [sqlite] sqlite3_step getting core dumbed.

try changing this: colNames = (char **)malloc(sizeof(char)); into something like colNames = (char **)malloc(sizeof(char * ) * noOfColumns); On 09.02.2012 11:21, bhaskarReddy wrote: HI Friends, I dont know why the sqlite3_step getting core dumped. #include #include

Re: [sqlite] Segmentation fault on sqlite3_create_module

>> > change this code: >> > typedef struct NiuRoutingStruct { >> > sqlite3_vtab vtab; >> > } NiuRouting; >> > to this: >> > struct NiuRouting : public sqlite3_vtab vtab { >> > ... // your implementation, eventually >> > }; >> > >> > This way, the casting is

Re: [sqlite] Segmentation fault on sqlite3_create_module

> Stephan Beal wrote: >> 2012/2/3 Jorge Eliécer Osorio Caro >> >> >*ppVTab = (sqlite3_vtab*) nr; >> > ((sqlite3_vtab*) nr)->zErrMsg = NULL; >> > >> >> Please try changing those to the variants from my previous post. i'm not >> 100% convinced that that cast is strictly

Re: [sqlite] Segmentation fault on sqlite3_create_module

> Marcus wrote: >> Just a guess: >> It looks you are compiling/using c++, on Windows that wouldn't work >> if the sqlite library is compiled as C (which is the usual case). >> >> So, you might have a calling convencion issue... >> >> Just a guess, though. > > The sqlite3.h header has proper,

Re: [sqlite] Segmentation fault on sqlite3_create_module

> Hi, > > I do this: > > const char *table_structure = "CREATE TABLE network (vertex_id INTEGER);"; > if (sqlite3_declare_vtab(db, table_structure) == SQLITE_OK) { > nr = (NiuRouting*) sqlite3_malloc(sizeof (NiuRouting)); > > if (nr == NULL) { >

Re: [sqlite] Speeding up Sqlite reads after DML

t think that you will be able to specify more than 2-3 GB cache, depending on your OS, unless you compile a 64 bit version of sqlite (I never did that). However, a 100 GB sqlite DB file should not be any problem, except the reported slow down. Marcus > > Thanks, > > Udi > > On T

Re: [sqlite] Speeding up Sqlite reads after DML

> Given how clever and compelling Sqlite is - I am testing how it scales to > tables in the 100GB / 200 million row range. This is for a strictly "read > only" application - but first the tables must be populated in a one time > process. As is often the case with Big Data - the data is a little

Re: [sqlite] PRAGMA journal_mode=WAL;

On 01.02.2012 11:10, Guy Terreault wrote: On 12-02-01 04:32 AM, Marcus Grimm wrote: On 01.02.2012 09:32, Guy Terreault wrote: On 12-02-01 03:03 AM, Larry Brasfield wrote: I cannot answer why Simon does not write demo code at every opportunity, but I think I speak for more than just myself

Re: [sqlite] PRAGMA journal_mode=WAL;

On 01.02.2012 09:32, Guy Terreault wrote: On 12-02-01 03:03 AM, Larry Brasfield wrote: I cannot answer why Simon does not write demo code at every opportunity, but I think I speak for more than just myself by revealing that I have other work, and a life, and consider time a scarce resource.

Re: [sqlite] Bug: SQLite Encryption Extension And Backup API

org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Marcus Grimm MedCom GmbH Darmstadt, Rundeturmstr. 12, 64283 Darmstadt Tel: +49(0)6151-95147-10 Fax: +49(0)6151-95147-20 web: www.medcom-online.de -- MedCom slogans of the

Re: [sqlite] Bug: SQLite Encryption Extension And Backup API

On 06.04.2011 14:21, Ulric Auger wrote: > Hi, > > I think I found a bug creating an encrypted backup. .. > > > > When I use the following function to create a backup of the database, the > backup database becomes unreadable. ... > > > >rc = sqlite3_open(zFilename,); > >if( rc==SQLITE_OK

Re: [sqlite] UPDATE/INSERTing 1-2k rows slower than expected

>> >> Interesting, I did a test on a 7200 file and the best I could do was 50 >> commits per second (a simple base/table with only id, journalling off >> and >> no >> extra code since the tool I use has "a repeated query" option with >> accurate >> timing). You mentioned 3 syncs per commit, but I

Re: [sqlite] UPDATE/INSERTing 1-2k rows slower than expected

> On Sat, Feb 12, 2011 at 9:48 PM, Marcus Grimm > <mgr...@medcom-online.de>wrote: > >> > I should've realized it wasn't running this fast but the small 5000 >> record >> > size got me. >> > Test it yourself. >> > I do have a 7200RPM drive.

Re: [sqlite] UPDATE/INSERTing 1-2k rows slower than expected

> OK...I added your trigger example as option 8. And I had pasted the wrong > version in my last email. My timings were correct. Your example also did > sql_exec instead of using prepare so it will run slower. Yes, but that should be marginal. When I send my code the trigger version wasn't

Re: [sqlite] UPDATE/INSERTing 1-2k rows slower than expected

> I fixed a couple of bugs in my program...I had converted from clock() to > the more appropriate gettimeofday and forgot to remove the CLOCKS_PER_SEC > factor (what's a few order of magnitude between friends :-). Plus I added > a 3rd argument so you can in-memory, index, and WAL mode too (or

Re: [sqlite] EXT :Re: UPDATE/INSERTing 1-2k rows slower than expected

Analytics Directorate > > > > > From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on > behalf of Marcus Grimm [mgr...@medcom-online.de] > Sent: Saturday, February 12, 2011 10:23 AM > To: General Discussion of SQLite

Re: [sqlite] UPDATE/INSERTing 1-2k rows slower than expected

> On Sat, Feb 12, 2011 at 9:10 AM, Black, Michael (IS) > > D:\SQLite>batch 5000 1 >> 360766.6 inserts per sec >> > > Unless I'm missing something, SQLite has to update the first page of the > database on every commit, to update the change counter. Assuming you are > using

Re: [sqlite] Help on DELETE FROM...

lect t2.ID from THI t2 where t2.UserID=UserID > order by t2.TimeStamp desc limit 100 offset 10); > > Michael D. Black > Senior Scientist > Advanced Analytics Directorate > Northrop Grumman Information Systems > > > > > From: sql

Re: [sqlite] Help on DELETE FROM...

rom thi where a.userid=thi.userid > ...> order by timestamp limit 100 offset 10); > 10|20|10|0 > 11|21|10|0 > 12|22|10|0 > 23|31|20|0 > 24|32|20|0 > 25|33|20|0 > > > Michael D. Black > Senior Scientist > Advanced Analytics Directorate > Northrop Grumman

Re: [sqlite] Help on DELETE FROM...

e > Northrop Grumman Information Systems > > > > > From: sqlite-users-boun...@sqlite.org on behalf of Marcus Grimm > Sent: Mon 1/17/2011 10:24 AM > To: General Discussion of SQLite Database > Subject: EXTERNAL:Re: [sqlite] Help on DELETE FROM... >

Re: [sqlite] Help on DELETE FROM...

On 17.01.2011 17:14, Igor Tandetnik wrote: > Marcus Grimm<mgr...@medcom-online.de> wrote: >> I have a table to record some history data, for example >> items a user recently selected: >> >> CREATE TABLE THI(ID INTEGER PRIMARY KEY, TimeStamp INTEGER, U

Re: [sqlite] Help on DELETE FROM...

; Advanced Analytics Directorate > Northrop Grumman Information Systems > > > ____ > > From: sqlite-users-boun...@sqlite.org on behalf of Marcus Grimm > Sent: Mon 1/17/2011 6:17 AM > To: General Discussion of SQLite Database > Subject: EXTERNAL:[sqlit

[sqlite] Help on DELETE FROM...

Hi List, sorry for not being very sqlite specific here but I would like to have an advice on a delete operation for which I can't find the right sql command. Currently I do it on C programming level using a loop but I think there must be a better sql way. Anyway, here is the story: I have a

Re: [sqlite] Windows performance problems associated with malloc()

..@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] > On Behalf Of Marcus Grimm > Sent: Saturday, December 18, 2010 5:31 AM > To: General Discussion of SQLite Database > Subject: EXTERNAL:Re: [sqlite] Windows performance problems associated > with > malloc() > >>

Re: [sqlite] Windows performance problems associated with malloc()

> I believe the Windows default is to use the LFH on Vista and newer > versions of Windows. > The suggestion by Marcus Grimm to use _set_sbh_threshold() to enable use > of the SBH (small block heap) may help under some usage scenarios on > those platforms. Jus

Re: [sqlite] Windows performance problems associated with malloc()

> An SQLite user has brought to our attention a performance issue in SQLite > that seems to be associated with malloc(). If you have insights or > corroborating experience with this issue please let me know. We recently had a malloc/free slowdown issue after changing to VS2008 in combination

[sqlite] No "PRAGMA default_cache_size" in 3.7.4 ?

. The docs doesn't mention what to use instead or did I missed something ? Kind regards Marcus Grimm ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] WAL mode and backup API

On 30.11.2010 11:50, Dan Kennedy wrote: > >> BTW: >> Is there any chance that in the future the wal mode >> will avoid that the backup API will restart on DB >> changes during the backup loop ? >> Currently, even in wal mode, it does restart when changes >> are detected while the backup is

Re: [sqlite] WAL mode and backup API

On 30.11.2010 11:32, Dan Kennedy wrote: > On 11/30/2010 05:03 PM, Marco Bambini wrote: >> Hello, >> >> if a running sqlite database is in WAL mode and a backup is performed on >> that db using the sqlite3_backup API, does that process is considered like a >> reader and can proceed concurrently

Re: [sqlite] Speed up DELETE of a lot of records

se it with .quit the -wal file is not reintegrated. > > Il 08/10/2010 9.56, Michele Pradella ha scritto: >>I'll try to increase cache size, and I'll try operation on my Db with >> the 3.7.3 anyway I already ported the Fix of the WAL issue from recent >> snapshot. I

Re: [sqlite] Speed up DELETE of a lot of records

Michele Pradella wrote: > As I explain in previews email, I think that recreating the index is > the slowest operation I can do on my DB. > Anyway in my first email I ask another question about -wal file > Tryin to DELETE the (5 millions) records with the shell SQLITE interface > I can see

Re: [sqlite] memory wasted shm mapped file (3.7.2)

Michele Pradella wrote: > ok, I'll wait for the walk around. > I always use a BEGIN; COMMIT; transaction but often, after a COMMIT; the > -wal file does not change in size, it seams it's not checkponted. > Anyway do you think that with WAL journal mode I should continue to use > BEGIN;

Re: [sqlite] Implementation check request

> > On 28 Aug 2010, at 4:24pm, Max Vlasov wrote: > >> I don't know whether my posts have a delay with delivery (replied >> several >> hours ago to the discussion you mentioned), but actually I tested 100 >> rows >> before and after with a similar query (ORDER BY LIMIT) and it definitely >> shows

Re: [sqlite] SQLite 3.7.0 coming soon....

I would be pleased to try that version, however I'm not sure if you already support the SEE extension ? At least I can't find it yet on the SEE Software Configuration System. Marcus Grimm D. Richard Hipp wrote: > We are in the final phases of development for SQLite version 3.7.0. > T

Re: [sqlite] Insert large data question ??

> Thanks Kishor ,I will note it !! > > I already used transaction to doing this job. > I tried to remove all of index ,this time the job used about 31600 seconds > > ps. I had use "PRAGMA synchronous=OFF" in front of my transaction. > > someone can help me do this job more faster ?? have you

Re: [sqlite] Is there any memory leak in the code while being busy?

it is not necessary to send your question multible times... ;) to answer: what makes you think that sqlite3_finalize can't free the prepared statement ? liubin liu wrote: > Is there any memory leak in the code? > > Below is the code. Is there any memory leak in the pthread2? > > While

Re: [sqlite] Fastest concurrent read-only performance (+ threads vsprocesses) [BUG?]

, but timing measures on the other hand are very difficult and I might be doing them wrong. In case the test program is of interested to anybody, here is the latest version: http://www.exomio.de/SqliteSpeedTest2.c Marcus Marcus Grimm wrote: > Hi Luke, > > > Luke Evans wrote: >> Hi

Re: [sqlite] Fastest concurrent read-only performance (+ threads vsprocesses) [BUG?]

there's absolutely no need for synchronisation with > activity on other threads - particularly for this read-only case. > For this small number of threads/queries (relative to the number of > processing cores I have), the difference is between 1.6s and 8.34s, which is > really qu

Re: [sqlite] Fastest concurrent read-only performance (+ threads vsprocesses) [BUG?]

I have followed the discussion about this issue with interest since my usage of sqlite involves threads and sharedcache mode as well. I have also generated a little speed test program that uses multible threads and shared cache to read *some* rows out of the sqlite DB. It might not help here but

Re: [sqlite] Prohibitive indexing time with large tables

aily basis couple of hours is a big price to pay. Jerome can > correct me, but he still didn't add anything new to this discussion, hope > he > will. His original question was about the todo list found at the wiki. Not sure if any of the core developer will answer, but I would be interested as

Re: [sqlite] Prohibitive indexing time with large tables

Just for my curiosity: Have you tried to increase the cache as already suggested ? I ran into a similar problem while playing with a artificial test database with appx. 10 Mio records and creating an index. Without drastically increasing the cache size sqlite appears not to be able to create an

Re: [sqlite] Nesting Read/Write within Transaction?

> >>The only thing that can bite you is if >>you are in process of fetching rows from some select statement and you >>update row that was just fetched or update/insert rows that would have >>been fetched later by the select statement. > > As I understand it, simply wrapping every batch operation

Re: [sqlite] german documentation

> Hi, > that's bad if i sound like an google translator. At the beginning i tried > to translate it as original as i could, now i translate it, ho wit sounds > good to me. Can you say me, which sites are bad translated? For example the chapter: Vorgeschlagene Benutzungsarten für SQLite this one

Re: [sqlite] german documentation

Hi, I mean a google like translator. As I said, partly. not all of this. I think you should not try to translate word by word, preserving even the original english sentence structure. The result sounds machine-like for a native german. But it is interesting as an exercise, if you define it this

Re: [sqlite] german documentation

> Hello, > > sorry for the double mail, but i cannot post to my old post. > > The german documentation is now on: > > http://sqlite.yuedream.de > > What do you think? Is the design good? this will be a lot of work and I'm wondering why you do this ? Despite beeing a german with a rather poor

Re: [sqlite] execute or prepare+step+finalize

you may also take a look at: http://www.sqlite.org/cvstrac/wiki?p=SimpleCode it explains how to use the step mechanism. hth Marcus > > > why not: > int smth = sqlite3_step (statement2); > while( smth == SQLITE_ROW ) > { > printf( "\n command= %s result code = %d \n",

Re: [sqlite] Deadlock with two local instances

> On Tue, 27 Oct 2009 21:50:12 +0100, "Marcus Grimm" > <mgr...@medcom-online.de> wrote: > >>PS: Does anybody know how I can edit this >>example code ? I recently attempted to add a clear >>PD statement and also add some comments but when >>I tr

Re: [sqlite] Deadlock with two local instances

llways end up in the wiki index page... > > On Tue, Oct 27, 2009 at 12:55 AM, Marcus Grimm <mgr...@medcom-online.de> > wrote: >>> Another odd thing is that when I call sqlite3_reset on the prepared >>> statement, it also returns SQLITE_BUSY.  Should I only reset t

Re: [sqlite] Deadlock with two local instances

ing. hth Marcus Grimm > > On Mon, Oct 26, 2009 at 2:40 PM, Chris T <citrus...@gmail.com> wrote: >> I'm new to sqlite (and sql in general, actually) and came across >> something puzzling. >> >> I wrote a test program statically linked with the amalgamated

Re: [sqlite] SQLite Suitability for Shopping Cart

I would like to add also a comment here: Sqlite perfectly works as a backend for multi user applications/servers IF they are implemented accordingly. That is, avoid multible processes/instances that access the same db file, use one main process and threads instead. Take care about busy handling

Re: [sqlite] Serious locking/blocking issue

> Igor Tandetnik wrote: >> Angus March wrote: >>> After the callback has finished, what will happen with that original >>> call to sqlite3_reset()? >>> >> >> Since sqlite3_reset doesn't take any locks, a busy callback would never >> be invoked for it. >> > > Well someone

Re: [sqlite] Memory leak on inserting from sqlite c/c++ interfaces

just a point: In your pseudocode you precreate statements for the begin and commit and trying to reuse them later on. If your real code is like this I would suggest to take a look at this. I think it is not possible to "re-step" a begin or commit, you may try to recreate these statements

Re: [sqlite] Repost: Accessing a DB while copying it causes Windows to eat virtual memory

I might missed that but: what are you trying to acomplish by using explorer to copy the database file ? I guess you are doing it for backup purpose. For this, be aware that it might be dangerous to do a simple file copy on a running database since you might forget some temporary files used by

Re: [sqlite] How can a COMMIT attempt result in SQLITE_BUSY ?

Thank's Igor, uhh... I should have read this more carefully. I understand now that the commit may in fact need to wait for some other shared locks... sorry for the noise Marcus > Marcus Grimm wrote: >> I'm wondering how it can happen that after a successfull >> "BEGIN TRA

[sqlite] How can a COMMIT attempt result in SQLITE_BUSY ?

is (mainly to really make sure that a COMMIT can't be timed out anymore) but I'm curious if there is an explanation for this. Thank you Marcus Grimm ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite3: Database is sometimes locked when a reader is attached with open_v2

mpt. Marcus > > Thanks > > Tino > > -- > > > Marcus Grimm wrote: > >> I'm afraid this is by design of sqlite: Sqlite will lock >> the database during a writing transaction, I think no matter >> if you open a 2nd connection using the readonly fl

Re: [sqlite] SQLite3: Database is sometimes locked when a reader is attached with open_v2

I'm afraid this is by design of sqlite: Sqlite will lock the database during a writing transaction, I think no matter if you open a 2nd connection using the readonly flag. the typical solutions are: a) retry your read attempt after you receive a busy error code until it proceeds. b) consider

Re: [sqlite] Python sqlite binding: commit inside select loop

thank you very much Richard! very interesting to get some info about these rather internal issues. This gives us a good background to review some potential dangerous loops. Your hint with the temp table is extremely useful. Best wishes Marcus Grimm > > On Jun 30, 2009, at 2:34 PM, Marcus

Re: [sqlite] Python sqlite binding: commit inside select loop

> Marcus Grimm <mgr...@medcom-online.de> wrote: >> what is possible I guess would be to start a transaction >> inside the loop, do something, and commit and procced >> with stepping > > No, this is not possible either. By starting the select, you also start

Re: [sqlite] Python sqlite binding: commit inside select loop

> Marcus Grimm <mgr...@medcom-online.de> wrote: >> I'm a bit confused about Igors replies because >> you can very well do a select, step throu the >> results and even delete or update the table row that you >> are currently inspecting and procceed with stepping. &

Re: [sqlite] Python sqlite binding: commit inside select loop

I'm a bit confused about Igors replies because you can very well do a select, step throu the results and even delete or update the table row that you are currently inspecting and procceed with stepping. As long as you use the same database connection for this. I'm not sure what will happend if

Re: [sqlite] Slow Transaction Speed?

> > On 31 May 2009, at 9:24pm, Jay A. Kreibich wrote: > >> The whole point of a transaction is that once it >> returns "success" on a commit, it is committed to permanent storage, >> no matter what -- including crashes, power failures, and other major >> problems. > > My impression is that

Re: [sqlite] Sqlite on a Virtual Machine of Microsoft's Hyper-V ?

it should be fine. > SQLite won't even know it is running on a virtual. > > Marcus Grimm wrote: >> Hello List, >> >> I've been asked if my server application will run >> in a virtual machine: Microsoft's Hyper-V >> I have no idea what this is, nor i

[sqlite] Sqlite on a Virtual Machine of Microsoft's Hyper-V ?

. Any experience with this ? Thank you in advance. Marcus Grimm ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Slow Transaction Speed?

> On Thu, May 28, 2009 at 03:12:55PM -0700, Allen Fowler scratched on the > wall: >> >> > just for anybody who is interested: >> >> > >> > I translated Jim's function into window code and added >> > a page of 1024 that will be written, instead of a single byte. >> > On my Win-XP system I got 55

Re: [sqlite] Slow Transaction Speed?

just for anybody who is interested: I translated Jim's function into window code and added a page of 1024 that will be written, instead of a single byte. On my Win-XP system I got 55 TPS, much faster than sqlite seems to write a page but that might be related to the additional overhead sqlite

Re: [sqlite] corrupt database recovery

encryption/compression code to > see > if I can get it to break. > > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Marcus Grimm > Sent: Wednesday, May 27, 2009 5:09 PM > To: 'General Discussion of SQLi

Re: [sqlite] corrupt database recovery

-Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Marcus Grimm > Sent: Wednesday, May 27, 2009 2:44 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] corrupt database recovery > > so, if you thi

Re: [sqlite] corrupt database recovery

so, if you think it is a coding error on your side it will be a hard work to find the source. I can only image side effects on an used API like sqlite3 with the classics: - stack frame overload in a function that calls sqlite functions - using a local stack variable as a return pointer and reuse

Re: [sqlite] Some index questions

27, 2009, at 10:13 PM, Marcus Grimm wrote: > ... >>> >>> WHERE b = 3 AND c = 4; >>> WHERE b = 3 AND c > 4; >>> >>> but cannot be used to optimize: >>> >>> WHERE c = 4; >> Ahh... I picked up the wrong example... Gre

Re: [sqlite] Some index questions

Richard, thanks you very much for the example and advice. Ahh, yes. I missed the point that sqlite might use an index also as a kind of buffer to fetch data. kind regards Marcus D. Richard Hipp wrote: > On May 27, 2009, at 11:13 AM, Marcus Grimm wrote: >> I guess such compound ind

Re: [sqlite] Some index questions

Hi Dan, thanks for your answers: this was exactly what I was looking for. Dan wrote: > On May 27, 2009, at 9:08 PM, Marcus Grimm wrote: >> >> The difference, I guess, to a "real" sql table, is that it is sorted >> with respect to the indexed column and not by row_i

Re: [sqlite] Some index questions

09 at 7:38 PM, Marcus Grimm <mgr...@medcom-online.de> wrote: >> Hi List, >> >> this is not very sqlite specific but hopefully somebody will give >> me some info on this, as I haven't yet found a nice description of this: >> >> I'm curios how an index works

[sqlite] Some index questions

y specific in the questions. Thanks Marcus Grimm ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Slow Transaction Speed?

Thanks Nick, good point. ahh yes, I've read about this somewhere... My extension is currently ".db", a quick check indicates that using ".abc" gives a slight speed improvement, maybe 10%. But that is allready very close to the variation I get between different test runs, so I'm not really sure

Re: [sqlite] Slow Transaction Speed?

the backup will usually take place around midnight. kind regards Marcus Nuno Lucas wrote: > On Wed, May 27, 2009 at 12:51 PM, Marcus Grimm <mgr...@medcom-online.de> > wrote: >> Yes, I understood that this is unsafe and I'll not use it right now. >> But my feeling is that it wi

Re: [sqlite] Slow Transaction Speed?

for my curiosity: Is linux considered to be faster than Windows here ? kind regards Marcus D. Richard Hipp wrote: > On May 27, 2009, at 7:51 AM, Marcus Grimm wrote: > >> >> Nuno Lucas wrote: >>> On Wed, May 27, 2009 at 5:58 AM, Marcus Grimm <mgr...@medcom-online.de &g

Re: [sqlite] Slow Transaction Speed?

Nuno Lucas wrote: > On Wed, May 27, 2009 at 5:58 AM, Marcus Grimm <mgr...@medcom-online.de> wrote: >>> On Tue, May 26, 2009 at 9:47 PM, Marcus Grimm <mgr...@medcom-online.de> >>> http://www.sqlite.org/faq.html#q19 >> the faq as well as the sp

  1   2   >