Re: [sqlite] Database locked version 3.3.17

Resolved the issue. My issue on the app side. I think the newer version is much faster. So much so that it changed timing characteristics and reveald a logic bug in my code. Appologies, Ken Ken <[EMAIL PROTECTED]> wrote: Hi all, Think I may have hit some form of

[sqlite] Database locked version 3.3.17

more details to reproduce a simple test case. Ken

Re: [sqlite] sql stack using sqlite

tbl = 'c'); Any ideas of a better way? Thanks, Ken Ken <[EMAIL PROTECTED]> wrote: Id like to get your ideas on implementing a stack using sql tables. table a, contains references to b table b contains refernce to a table c contains delete entries for A (but b

[sqlite] sql stack using sqlite

using sql. thanks for any ideas. Ken

Re: [sqlite] perfomance degradation for expr "foo = X or bar =X"

. -- D. Richard Hipp I think that is a good thing that sqlite isn't that clever! I've seen too many cases of advanced optimizers such as Oracle totally mess up the execution plans for complex query operations. There are simply too many choices for the optimizer to pick the best plan. Ken

Re: [sqlite] reseting primary key

DRH SAID: [EMAIL PROTECTED] wrote:The details of the UPDATE or DELETE are left as an exercise for the reader. Excellent, it reminds me of High School integral proofs. Q.E.D.

Re: [sqlite] Starving for New User Information

The .a file is for static linking. The .sl file is for dynamic linking (shared library) The .lib file is hidden because you were supposed to do a "make install" after make which would install the .libs into whatever "prefix" you gave to configure... Static linking makes it easier for

Re: [sqlite] May I ask why the source distribution mechanism was changed starting with 3.3.14?

time gcc -m32 -O2 -I. -I../sqliteSrc/sqlite-3.3.17/src -DNDEBUG -DTHREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c sqlite3.c -fPIC -DPIC -o .libs/sqlite3.o real0m20.266s user0m19.773s sys 0m0.444s time gcc -m32 -O2 -I.

Re: [sqlite] May I ask why the source distribution mechanism was changed starting with 3.3.14?

100% concur with Dennis. Thanks again for a great product! Dennis Cote <[EMAIL PROTECTED]> wrote: [EMAIL PROTECTED] wrote: > > Can somebody please explain to my how 2 files is less manageable > than 60? > > > Richard, I think part of the problem is simple inertia. Some people have

Re: [sqlite] Makefile

Thanks Tom, That was just what I was looking for Regards, Ken Tomash Brechko <[EMAIL PROTECTED]> wrote: On Wed, May 02, 2007 at 11:43:04 -0700, Ken wrote: > Is there a way to disable the -g flag for the library? Assuming you are using configure, ./configure CF

[sqlite] Makefile

? If not this would be really nice. Can the Make that is provided build a libsqlite3.a and libsqlite3.so from the amalgamated sqlite3.c ??? Thanks Ken

Re: [sqlite] 2 Threads - lock after Commit:

Matthew Veenstra <[EMAIL PROTECTED]> wrote: Hello, I was wondering if someone can shed a bit of light on a problem I am having. I am using SQLite in a client setting on Mac and Windows. I have two threads. That I use SQLite in. The main thread uses this to get data and display it to screen.

Re: [sqlite] what do I compile with -dthreadsafe=1

configure --enable-threadsafe should do it. Rafi Cohen <[EMAIL PROTECTED]> wrote: Hi, when I read the article about sqlite and multithread in cvstrac, I understood that I need to compile my source files using sqlite functions with -DTHREADSAFE=1. Now, due to a pproblem I had in my project I

Re: [sqlite] Re: SQLite and nested transactions

and really requires the concept of a transaction ID. Maybe this is specific to the DB vendor (ORA$$) I totally agree, in more than 20 years of commercial db development and DBA work, I've only encounterd the use of savepoints 1 time. Dennis Cote <[EMAIL PROTECTED]> wrote: Ken

Re: [sqlite] Re: SQLite and nested transactions

us far are not very compelling for savepoints. But savepoints are usefull in special situations. Instead of Nested Transactions, What about the concept of an autonomous transaction? Regards, Ken

Re: [sqlite] Data structure

You might want to check out kazlib for your data structure lookups. It cantains code to implement Linked List, Hast, and Dictionary access data structures. The hashing code is really quite fast for in memory retrievals plus it is dynamic so that you don't have to preconfigure your

Re: [sqlite] Data structure

is an excellent tool. Ken Lloyd <[EMAIL PROTECTED]> wrote: Would anybody suggest a good tool for performance measurement (on Linux) ? On Wed, 2007-04-11 at 10:35 -0500, John Stanton wrote: > You might discover that you can craft a very effective memory > resident > stora

Re: [sqlite] SQL help

sum(is_complete) is only the same as "where is_complete = 1" when there is a check constraint guaranteeing that is complete will either be a 0 or 1. Dennis Cote <[EMAIL PROTECTED]> wrote: Clark Christensen wrote: > I have a table, as described below, where I need to find out if the tech_id

Re: [sqlite] SQL language issue, ticket #2282

Oracle does not allow a when clause on an instead of trigger. when new.key=old.key * ERROR at line 3: ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers [EMAIL PROTECTED] wrote: Ticket #2282 against SQLite http://www.sqlite.org/cvstrac/tktview?tn=2282 complains

Re: [sqlite] in-memory database bound to a named buffer

short answer is no. The memory structures are not identical to disk structures. Ryan Underwood <[EMAIL PROTECTED]> wrote: Is it possible to bind an in-memory sqlite database (in read-only mode, naturally) to an existing named memory buffer that contains exactly the contents of a sqlite

Re: [sqlite] PLSQL

John, I've used PL/SQL on Oracle. I think it was derived from another language, maybe PL/1. I think its an excellent language, my main usage was geared at PL/SQL for DBA usage that managed internal oracle objects. Pros: Packages / Procedures/ Functions have a really nice hierarchy.

Re: [sqlite] Difference in these indices?

storage-clause := store as (fileName, pageSize, initialAlocation) Ken Joe Wilson <[EMAIL PROTECTED]> wrote: --- [EMAIL PROTECTED] wrote: > If you insert records in order of ascending integer primary > key, then the inserts will be very fast. If you insert rec

Re: [sqlite] Use of bind variable in sqlite

concurrency you'd better stick with oracle. Sqlite is designed for embedded single users systems. Regards, Ken "Amarjeet Kumar (RBIN/ECM4)" <[EMAIL PROTECTED]> wrote: Hi, Can we use the bind variable in sqlite query, if so how? Thanks in advance. Regards, Amar

Re: [sqlite] Finding linked peers

Sample recusrive SQL from another database engine... level is a built in field. This is very useful and powerful syntax allowing one to build tree's (ie parent child relationships) inside of a table. SELECT level,chld FROM tbl1 START WITH value = 'some value'

Re: [sqlite] API enhancement

Denis, Thanks for the great explanation !!! Regards, Ken Dennis Cote <[EMAIL PROTECTED]> wrote: Ken wrote: > It should save some time. How much is questionable. > > Why would sqlite have to bind the Pointer bound variables? Isn't the strategy > of bi

Re: [sqlite] API enhancement

You've superficially lifted some code out of the loop, but sqlite3_step() is going to have to go through and bind all of the "pointer bound" variables in your suggested API, so it won't save you anything in the end. -scott On 3/19/07, ken-33 wrote: > > Anyone thoughts? > > >

Re: [sqlite] API enhancement

Anyone thoughts? ken-33 wrote: > > Question for the list, > > I'd like to optimize my code, using the following pseudo code as an > example. > > === > int i = 0 ; > char str[20]; > > sqlite3_p

Re: [sqlite] API enhancement

Anyone Ken <[EMAIL PROTECTED]> wrote: Question for the list, I'd like to optimize my code, using the following pseudo code as an example. === int i = 0 ; char str[20]; sqlite3_prepare_v2( "insert into t1 values (?,?)" ) sqli

Re: [sqlite] Strange performance behavior

Did you ever determine the cardinality of the campID field? I'm guessing its pretty good since your query is now .6 seconds. Lets say your cardinality was low, ie say less than .3 (arbitrary number). Then using the index to perform you data lookups would probably be slower than just reading

Re: [sqlite] Strange performance behavior

Looks like it is going to do a full scan of the entire database to complete that querry based upon your where clause. Are you always accessing the data by campID? What is the cardinality of campId data? Depending upon that it might be worth while putting and index on CampID. Hubertus

Re: [sqlite] sqlite Performance

b5 to purge is a simple detach and operating system unlink for the underlying datafile. Which I suspect will be infinately faster than a sql delete command. Thanks, Ken Dennis Cote <[EMAIL PROTECTED]> wrote: Ken wrote: > > This is a write only app. 100% insert. >

Re: [sqlite] sqlite Performance

DRH, Thanks for your valuable insite. When the DB is closed when in synchrounous mode, is it then persistent at the OS level even from power failures etc? [EMAIL PROTECTED] wrote: Ken wrote: > > I should be able to run with synchronous=off. Since > the application

Re: [sqlite] How to set pragma page_size

Thanks DRH... That worked. Ken [EMAIL PROTECTED] wrote: Ken wrote: > How does one set the page_size ? > > according to the documentation > "The page-size may only be set if the database has not yet been created. > " > > So how do you execute the

Re: [sqlite] sqlite Performance

Tito, Its even better now! Synchronous=normal and No primary keys (except 1 table) for auto increment. real0m1.975s user0m1.436s sys 0m0.140s Vs flat file test case: real0m0.862s user0m0.228s sys 0m0.188s This is now very respectable. Thanks, Ken

Re: [sqlite] sqlite Performance

. This was definately an I/O issue and related to the code path vs say a select where the optimizer picked an incorrect plan. Regards, Ken Tito Ciuro <[EMAIL PROTECTED]> wrote: Hello, IIRC (it was a while ago), one way to speed up insertion for large data sets is to drop the index

[sqlite] How to set pragma page_size

How does one set the page_size ? according to the documentation "The page-size may only be set if the database has not yet been created. " So how do you execute the pragma prior to creating the DB? without calling sqlite3_open to get a DB handle that is needed to call prepare/step ?

RE: [sqlite] sqlite Performance

0m2.276s sys 0m0.136s Running with synchronous=off is 43% faster !!! Running with Synchrounous=normal is 33 % faster. I should be able to run with synchronous=off. Since the application maintains state in a seperate DB elsewhere. Thanks for you valuable Input. Ken

Re: [sqlite] sqlite Performance

Scott, The whole job is wrapped in an explicit transaction. Variables are bound and statements prepared only once, using reset. This is a write only app. 100% insert. Ken Scott Hess <[EMAIL PROTECTED]> wrote: Are you using explicit transactions at all? If not, as a quic

RE: [sqlite] sqlite Performance

ok my bad for poor wording... I'll try with Synchronous off. I may also try disabling the journal file since I can easily recreate the data if it is not successful. Thanks, Ken "Griggs, Donald" <[EMAIL PROTECTED]> wrote: Regarding: Creation of flat file takes 1.5 s

Re: [sqlite] sqlite Performance

is around .75 seconds (no write i/o).. So using a flat file output costs about .7 seconds. Using sqlite to do the output costs about 2.25 seconds. My question is why? And what can be done to improve this performance? John Stanton <[EMAIL PROTECTED]> wrote: Ken wrote: > I'

[sqlite] sqlite Performance

default_synchronous=FULL PRAGMA temp_store=memory PRAGMA page_size=4096 PRAGMA cache_size=2000 Any ideas how to get the sqlite output timings to a more respectable level would be appreciated. Thanks Ken

[sqlite] API enhancement

, int *, void(*)(void*)); Concept of SQLITE_STATIC vs SQLITE_TRANSIENT is implied that all data is SQLITE_STATIC. Regards, Ken

[sqlite] Link error with -DSQLITE_OMIT_TRIGGER

Compile error with -DSQLITE_OMIT_TRIGGER I get a link error when using: -DSQLITE_OMIT_TRIGGER === gcc -g -DSQLITE_DEFAULT_PAGE_SIZE=8192 -DSQLITE_DEFAULT_CACHE_SIZE=4000 -DSQLITE_OMIT_SHARED_CACHE -DSQLITE_OMIT_AUTHORIZATION -DSQLITE_OMIT_VIRTUAL_TABLE

Re: [sqlite] database is locked error with 3.3.13

I have the following sources which one would you like? sqlite-2.8.16.tag.gz sqlite-3.3.8.tar.gz sqlite-3.2.2.tar.gz sqlite-3.3.9.tar.gz sqlite-3.2.8.tar.gz sqlite-3.3.10.tar.gz sqlite-3.3.12.tar.gz sqlite-3.3.13.tar.gz sqlite-3.3.5.tar.gz sqlite-3.3.7.tar.gz Ken T <[EM

[sqlite] not sqlite question, but design ? for IoMethod & os_????.c

building an interface into os system calls such as open/fopen read/fread and i'd like to be able to have the calling code dynamically set up which interace to use, so I'm trying to get a handle on the above code as a roadmap... Thanks, Ken

Re: [sqlite] use of sqlite in a multithread C application

I found that although sqlite claims thread safeness it is actually in your hands to implement a thread safe access pattern. Here is how I implemented my sqlite thread saftey. Each thread opens its on connection. All operations begin with a do { BEGIN EXCLUSIVE

Re: [sqlite] (newbie) pictures in tables, what's the best way ?

This is a design question really so here are my recomendations. Persons - ID( an integer primary key ) - Name - Birthday - Picture Type ( your two digit type). Picture - ID (An integer Primary Key that matches the ID of persons). - image (blob)

Re: [sqlite] Atomically creating a database and bootstrapping its tables

To bootstrap my db's I create a database template. Then make a physical copy of that. Locking and access is done via flock. So the first process to gain the lock wins and is respoonsible for making the copy, the other just waits until the lock is released and then connects. I make lots of

Re: Re[2]: [sqlite] how can i speed up inserts ?

Try without the pragma and wrap the inserts with a begin transaction and a commit... The performance will be almost as good as with the pragma, with the added benefit of consistent data and no corruption in the event of a crash or power failure. DragonK <[EMAIL PROTECTED]> wrote:

Re: [sqlite] database is locked (my solution)

at the beginning of a transaction instead of during the middle. You can open a ticket by going into http://www.sqlite.org/cvstrac/wiki and clicking on ticket. Ken Andrew Teirney <[EMAIL PROTECTED]> wrote: > Andrew, > > Nice modification.. Did you buy

Re: [sqlite] database is locked (my solution)

Andrew, Nice modification.. Did you buy any chance post this into the sqlite ticketing system? It would be nice if sqlite would let you acquire a shared lock via the BEGIN statement. Andrew Teirney <[EMAIL PROTECTED]> wrote: > I have multiple thread reading the database and a

Re: [sqlite] Auto-detection of database change in multi-process environment

As I see it you have only 3 options. 1. Polling. Polling on a table in sqlite or depending upon your app. You could simply check the file access modifiers to see when the last modifaction time was. 2. Set up an IPC semaphore 3. Set up a socket. David GIGUET <[EMAIL PROTECTED]>

Re: [sqlite] How to specify collating sequences in an expression.

select x, y, z from t1 where collate binary x = y ; collating_expr ::= [collate ] expr ; The collating expression would apply to both x and y. [EMAIL PROTECTED] wrote: Dennis Cote wrote: > > In the standard character strings have a couple of attributes, a > character

Re: [sqlite] How to specify collating sequences in an expression.

the function is applied to the join attributes that match... IMHO the cast is the way to go to assign a collating sequence. Maybe you need an additional index type ? One where the index is specified with a function. Ken [EMAIL PROTECTED] wrote: "Igor Tandetnik" wrote: &

Re: [sqlite] How to specify collating sequences in an expression.

ult" attribute. Ken

Re: [sqlite] How to specify collating sequences in an expression.

If you are dealing with say a chinese char set then wouldn't you want to handle this at a "global" level by modifying the database characteristics, then maybe a Pragma command would be the way to go. [EMAIL PROTECTED] wrote: Ken wrote: > DRH and Sqlite Community, > &

Re: [sqlite] How to specify collating sequences in an expression.

of an "alter session" command (Similar to a sqlite PRAGMA). Regards, Ken [EMAIL PROTECTED] wrote: SQLite has supported collating sequences since version 3.0.0. A collating sequence is really a specification on how comparison operators work on strings. You can have

Re: [sqlite] Segfault when querying deeply nested view

I reproduced this as well on Suse 10 and 3.3.7 Using the following data: insert into records values ( date('NOW'), 'D/D', 'NPOWER','20','test acc','123456') ; insert into records values(date('2006-01-12'), 'D/D', 'NPOWER','20','test acc','123456') ; insert into records

Re: [sqlite] Re: Shared Lock Transactions

>From os_unix.h:... After reading this, locking makes more sense! Although the Lock may physically be an exclusive lock, the implementation is actually a logcially "SHARED" lock. /* The following describes the implementation of the various locks and ** lock transitions in terms

RE: RE: [sqlite] DROP INDEX not freeing up memory

Do you have to drop the index? Why not just keep it around, its obviously useful if you need to create it in the first place right? Dave Gierok <[EMAIL PROTECTED]> wrote: It does in fact look like the memory isn't being freed up entirely. I am properly tracking xMalloc, xRealloc, and

RE: [sqlite] DROP INDEX not freeing up memory

If you are using the OS to determine if memory is freed then perhaps that is where the problem lies. Many operating systems do not return memory back to the OS after a call to free. Instead the process will retain that in a "free pool" for later re-allocation. Ken Dave Gier

Re: [sqlite] Pager modification question

. But a bit more concurrent access. Ken John Stanton <[EMAIL PROTECTED]> wrote: If you want to share a file you have to be able to synchronize access in some way. The POSIX type file locks permit you to do it quite well by giving read and write locks. If you want shared

Re: [sqlite] Pager modification question

If it is a replacement for fopen, then why does it perform locking at all? Since sqlite has implemented threading and multiple connections, then the next logical step in its evoloution is to enable advanced locking techniques for even greater degrees of improved concurrency. Ken John

Re: [sqlite] Pager modification question

multiple thread with a higher concurrency level by using page level locking (or row level for that matter). Either way I think its a great piece of software. Thanks DRH. Christian Smith <[EMAIL PROTECTED]> wrote: Ken uttered: > Would it be possible to implement a Page leve

Re: [sqlite] Pager modification question

Regarding the Journal: I was thinking that this would be useful in the context of a single process multiple threads and shared cache. All that would be required is an additional thread to handle the logging. Christian Smith <[EMAIL PROTECTED]> wrote: Ken uttered: > Would it be

Re: [sqlite] How to handle dual-field Primary Key - only one is Autoincrement

Besides the trigger issue with sqlite. I think you have a design issue with your tables. You are using a composite key. Why not have a master table of customer I'ds that you maintain, whith only the customer_id as the PK and autoincrement. The the table you refer to would then be a child

Re: [sqlite] Sqlite Preprocessor

>From the standpoint of data insertions you wouldn't reall need to deal with >datatype correctness since sqlite is typeless. John Stanton <[EMAIL PROTECTED]> wrote: Why would it be a benefit? You would have to be doing type conversions all the time. Ken wrote: > I

Re: [sqlite] Sqlite Preprocessor

de you mentioned. Either you have to supply the column type info, or the tool has to obtain it somehow. And considering that SQLite is typeless, you have your work cut out for you. But don't let my contempt of SQL code generators disuade you. --- Ken wrote: > yes thats what I'm thinking..

[sqlite] Pager modification question

of tokenize is very interesting, what an excelent technique to embedd the tokens using overlapping strings. Can you send me an email address, I have some code that you might find intersting to utilze in the pager.c for the checksums. Ken

Re: [sqlite] Sqlite Preprocessor

Yes, but probably simpler and more in the tradition of sqlite. Make it simple and easy to use. John Stanton <[EMAIL PROTECTED]> wrote: Are you proposing an implementation of the existing Embedded SQL standard? Ken wrote: > Yes, a pre processor, but not a wrapper. A wrapper as I've

Re: [sqlite] Sqlite Preprocessor

that bit. There's no real need to connect to a sqlitedb just to verify the table exists. Ken Joe Wilson <[EMAIL PROTECTED]> wrote: > Yes, a pre processor, but not a wrapper. A wrapper as I've seen from the sqlite.org site is > simply a layer on top of the sqlite3 api. I've wr

Re: [sqlite] Sqlite Preprocessor

official one > within the database itself. > > There are, however, dozens of bindings to computer languages > in addition to the Tcl wrapper that ships with sqlite: > > http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers > http://www.sqlite.org/tclsqlite.html > > --- Ken

[sqlite] Sqlite Preprocessor

ing sqlStr; SQLITE_EXEC at :loginhndl bind x (not sure about this one) SQLITE_EXEC at :loginhndl fetch c1 into :hostvars ; SQLITE_EXEC at :loginhndl close cursor c1; SQLITE_EXEC at :loginhndl close database . The list would go on and on, but you get the idea. Ken

[sqlite] Sqlite Preprocessor

ing sqlStr; SQLITE_EXEC at :loginhndl bind x (not sure about this one) SQLITE_EXEC at :loginhndl fetch c1 into :hostvars ; SQLITE_EXEC at :loginhndl close cursor c1; SQLITE_EXEC at :loginhndl close database . The list would go on and on, but you get the idea. Regards, Ke

Re: [sqlite] Shared cache mode issue

Here is a code snipet from my version if the server thread code I found that it was doing an enable/disable on the shared cache with the original logic. You could always implement a sqlite3_open call and store it in the g variable, and close it when the server quits. void

Re: [sqlite] Segfault on sqlite3_reset

If sqlite3_finalize is the destructor, then what happens when it returns sqlite3_busy ? Should finalize be called again? Thanks [EMAIL PROTECTED] wrote: Ken wrote: > sqlite3_step > sqlite3_finalize > sqlite3_reset > > Ok I think I know.. the reset should not h

Re: [sqlite] Segfault on sqlite3_reset

f you get a SQLITE_BUSY on finalizing [EMAIL PROTECTED] wrote: Ken wrote: > Found the issue: > > > Called sqlite3_finalize after recieving a SQLITE_BUSY on on sqlite3_step, > then you get a segfault

Re: [sqlite] Segfault on sqlite3_reset

prepared the statement. Why can't it be reset of finalized if a sqlite busy is encountered ??? Ken Ken <[EMAIL PROTECTED]> wrote: I'm getting a segfault and sigabort (sporadic) when calling sqlite3_reset. Version 3.3.9 and using sqlite3_prepare_v2... I'll retest

[sqlite] Segfault on sqlite3_reset

I'm getting a segfault and sigabort (sporadic) when calling sqlite3_reset. Version 3.3.9 and using sqlite3_prepare_v2... I'll retest using sqlite3_prepare. Ken

Re: [sqlite] When to release version 3.3.10?

I concurr with Dennis. Dennis Cote <[EMAIL PROTECTED]> wrote: [EMAIL PROTECTED] wrote: > The question is: should I rush out 3.3.10 to cover this important > bug fix, wait a week to see if any other bugs surface, or do the > usual 1-2 month release schedule and let people effected by this >

Re: [sqlite] sqlite performance, locking & threading

Emerson, I agree with you somewhat. Not 100% convinced but, I like you am a little dissapointed how sqlite handles "threadsafe" and multiple connections. Even in the "test_server.c" module is not "concurrent" As it serializes all processing to a single thread, this is not concurrent

Re: [sqlite] SegFault on threadtest2.c using version 3.3.9

What other tests? [EMAIL PROTECTED] wrote: Ken wrote: > threadtest2 generated a segmentation fault as well as an illegal operations > when running against version 3.3.9 (in 32bit mode). > > I did compile using --enable-threadsafe. > > Does this mean this version

Re: [sqlite] pragma read_uncommitted and threading

the server to filter, based upon the thread id's this saves a small amount of time due to not recalling the sqlite3 functions just to get another server is locked message. Ken <[EMAIL PROTECTED]> wrote: I ran everything through the test_server "server" and get the following re

Re: [sqlite] Joining tables in a single file

I think the attach is the way to go, but no need to insert, just select from the attached databases. sqlite3 master.db (master is empty). attach a.db A attach b.db B attach c.db C Then : select from a.A, b.b, c.c where Alberto Simões <[EMAIL PROTECTED]>

Re: [sqlite] pragma read_uncommitted and threading

n and find out if my code is incorrect or if I've hit a bug. Thanks, Ken [EMAIL PROTECTED] wrote: Ken wrote: > > My thought was that if i wanted to perform selects concurrently on SMP > system I would need 2 threads and each thread would be able to read > concurrentl

Re: [sqlite] Creating a database from inside a program

I have a nice solution that really works well, at least from C... 1. Create a template Database. (using whatever method you like, either embedded in your code or via sqlite3). 2. Copy the database to a new file, using plane old cp, copy, or if you like an in code copy using open,

Re: [sqlite] sqlite performance, locking & thread

support. Emerson Clarke <[EMAIL PROTECTED]> wrote: Ken, Yes you cannot have multiple threads within the same transaction, and you cannot pass a connection between threads. I think we have an undestanding about the performance situation, and we are getting to the real heart of the issue,

[sqlite] pragma read_uncommitted and threading

Hi all, I have a piece of code that utilizes test_server.c, (master thread) there are 3 threads, each performing seperate tasks, that get a conection (shared) and set PRAGMA read_uncommitted=1. My understanding is that this would allow each individual thread to

Re: [sqlite] sqlite performance, locking & threadi

of locking internally, either page locking, row locking etc.. Sqlite uses Database LOCKING, which is full file. So its really only designed to be used by a single thread of execution. (again DRH please correct me here if I'm wrong). Emerson Clarke <[EMAIL PROTECTED]> wrote: Ken, Thanks.

Re: [sqlite] sqlite performance, locking & threadin

sqlite if it doesn't fit your needs. Emerson Clarke <[EMAIL PROTECTED]> wrote: Ken, Thanks i understand your example well. What im looking for is the ability to have multiple threads perform a write operation based on my mutex, not some internal sqlite write mutex. If i am ma

Re: [sqlite] sqlite performance, locking & threading

actually improves performance. Hope this helps, Ken Emerson Clarke <[EMAIL PROTECTED]> wrote: Roger, Thanks for the suggestions. I think using a worker thread and a queue would be equivalent to just running a single thread since it effectively makes the database oper

Re: [sqlite] delayed (batch) transactions

Regarding Oracle: It also batches commits... This means that if two or more users submit commits concurrently (or near the same interupt ) then those will be serviced at the same time. But oracle differs significantly from sqlite, in its architecture as it would not be appropriate for an

Re: [sqlite] Re: server and threading

ld be improved over a full write lock at a global level. Any other paradigms or thoughts about this? Thanks Igor Tandetnik <[EMAIL PROTECTED]> wrote: Ken wrote: > I've been looking at the server.c file. And have started some > testing. I'd like to know if the server.c (sin

Re: [sqlite] Re: server and threading

sql Begin begin2 No -op, cntr > 1 commit 1 sql Commit & sql begin. commit 0 sql commit Igor Tandetnik <[EMAIL PROTECTED]> wrote: Ken wrote: > I've been looking

[sqlite] server and threading

really seem to work. I get success on 4 concurrent threads. Then later get a commit failure indicating "no transaction active".. Thanks for your help. Ken

[sqlite] SQLite 3.3.1

Hmmm. The number of warnings compiling the 3.3.1 source is up to 10 from 6 in the 3.3.0 source. All of them appear to be related to inappropriate sign comparisons/assignments. -ken

Re: [sqlite] Problem executing SQLite 3.3.0 under MacOS

the optimization level, and the problem disappeared -- the code is working as before! I have adjusted the code so that the debug mode has optimization turned off, but that it is still enabled in release mode. Thanks once again. -ken On 13-Jan-06, at 8:40 PM, [EMAIL PROTECTED] wrote: Try

Re: [sqlite] Problem executing SQLite 3.3.0 under MacOS

. I am stuck! How do I resolve this problem and get the 3.3.0 code working once more? -ken On 12-Jan-06, at 11:52 PM, [EMAIL PROTECTED] wrote: The whole OS-backend was reworked for version 3.3.0. So do not expect to find the same functions in 3.3.0 that you had in 3.2.8. unixLock

Re: [sqlite] Problem executing SQLite 3.3.0 under MacOS

attempt to debug the 3.3.0 source and step into the sqlite3OsLock call, it simply drops me into some assembler and declares the bad instruction signal. -ken On 12-Jan-06, at 8:46 PM, [EMAIL PROTECTED] wrote: Ken & Deb Allen <[EMAIL PROTECTED]> wrote: I had a look, but I do not

[sqlite] Problem executing SQLite 3.3.0 under MacOS

I have encountered a problem while attempting to execute some code with SQLite embedded. This code was working with the previous version of the source. I am developing a small framework to permit me to use the SQLite engine from within some Cocoa applications I am developing for personal

<    1   2   3   4   5   6   >