ounter some
sort of issue with DB.
So my (might I say holistic view) question is if sqlite3_exec is unable to
differentiate a busy_handler trigger due to permission other related issues
and DB lock, won't we get ourselves into some mis-leading (ambiguity)
scenario.
Regards,
Kiran
-
Does this mean that the "shared_cached" connections in two threads can access
the same DB cache and database in parallel?
I'm all for it, either way it should be an improvement.
Thanks DRH for a great product.
Ken
[EMAIL PROTECTED] wrote: We are considering a change to the S
134 2007-08-09 18:40 bat_412.db-mj514651E0
Thanks,
Ken
size is 4k.
Cache size is 4000.
locking_mode = exclusive.
Synchronous off
Is there any way to disable journaling?
I can always re-create the DB should anything fail.
Any other ideas on how to make this run quicker?
Thanks,
Ken
uffer:
insert into x
commit;
Could the overhead of memory allocation acount for the variances? Is there
any way to pin the sqlite allocated pages into the Master DB's cache? Sort of a
sub cached allocation so that attached DB's do not require malloc/free for
memory pages?
Joe,
Yes I have temp_store = memory... I think during the compilation of the
library.
I don't think I need the order by clause but I'll try it just to see if it
helps...
The original table is created and stored in sorted order so just a plain
select returns sorted rows.
I'll
in 2 places, actually creating the original and for
the copy component.
Thanks for your patience and allowing me to bounce ideas.
Ken
Joe Wilson <[EMAIL PROTECTED]> wrote: Forget about the alternate insert
statements I suggested.
Assuming "id" is declared INTEGER PRIMARY K
It should not.
As long as those two connections are not used across threads and point to
truely different databases.
They wouldn't be a soft link would they? I
Mark Brown <[EMAIL PROTECTED]> wrote: Hi John-
There is a .lock file for each database. From my understanding, that should
prohibit
wide mutex for thread synchronization and see if
that improves our results. I'm still thinking our problems may be low-level
file i/o bugs with our OS, so perhaps taking out the file-based .lock scheme
will help.
Thanks,
Mark
> -Original Message-
> From: Ken [mailto:[EMAIL PROTECTED]
>
y errors during your inserts or commit operations. But the thread
wrting thread should eventually be able to acquire the lock and continue as
long as the reading threads close off their locks before the writer times out.
HTH.
Ken
I think method 3 shows the best promise:
Obviously M4 is out since it is in memory only. Besides caching should help
improve the performance.
The qustion that begs to be asked is: What are your performance goals? And
what are your performance numbers ie timings for each of the mehtods
ranlib .libs/libsqlite3.a
creating libsqlite3.la
(cd .libs && rm -f libsqlite3.la && ln -s ../libsqlite3.la libsqlite3.la)
./libtool --mode=link gcc -g -O2 -I. -I../src -DNDEBUG -DTHREADSAFE=1
-DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1
-DHAVE_READLINE=1 -I/usr/include/read
- Error Here
releasePage(pOldPage);
pCur->pPage = pNewPage;
pCur->idx = 0;
pCur->info.nSize = 0;
Ken
:3304
(gdb)
if( rc ) return rc;
pNewPage->idxParent = pCur->idx;
pOldPage = pCur->pPage;
pOldPage->idxShift = 0; < Error Here
releasePage(pOldPage);
pCur->pPage = pNewPage;
pCur->idx = 0;
pCur->info.nSize = 0;
Ken
413 in sqlite3OsWrite (id=0x55aaa0, pBuf=0x401ffc30, amt=24,
offset=0) at os.c:38
(gdb) Quit
(gdb)
Ken <[EMAIL PROTECTED]> wrote: 4 threads, shared_Cache enabled
LOOP 100
BEGIN
LOOP 50 times
INSERT
end LOOP
COMMIT
SELECT COUNT(*) ...
end LOOP
program received si
]> wrote:
Hi Ken,
Probably a bug in the new threading stuff. Can you share
source code for this test or is it part of some large app?
Either way, thanks for the report.
Dan.
On Wed, 2007-08-29 at 22:15 -0700, Ken wrote:
> Also erros out here, sporadically.
> int sqlite3OsWrite(sqlite
http://www.sqlite.org/lockingv3.html
where A3 means the processes 3rd connection.
A1 - Shared (select)
B2 - Pending (insert)
A3 - Shared (select)
Looks like a deadlock at A3. B2 has a pending Lock and can not make further
progress until A1 completes. But A3 is now waiting on B2.
Eith
** $Id: btree.c,v 1.420 2007/08/30 01:19:59 drh Exp $
Compilation:
../configure --enable-threadsafe --disable-tcl --enable-tempstore
make
gcc -g -O2 -I. -I../src -DNDEBUG -DTHREADSAFE=1
-DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c
../src/alter.c -o alter.o >/dev/null 2
Recompiled with:
gcc -DSQLITE_THREADSAFE -I. -I../src -DSQLITE_DEBUG=1 -DTHREADSAFE=1
-DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1
-DHAVE_READLINE=1
Ran code (hardware is a dual core x86_64 amd cpu).
sqlitetest_thrd35: ../src/btree.c:1816: sqlite3BtreeBeginTrans: Assertio
And the sqliteInt.h file is id as:
** @(#) $Id: sqliteInt.h,v 1.605 2007/08/29 12:31:28 danielk1977 Exp $
Let me know if you need anything else..
Thanks,
Ken
[EMAIL PROTECTED] wrote: Joe Wilson wrote:
>
> latest CVS:
>
> #if SQLITE_THREADSAFE
> # include
> # define SQL
ree.c:2494: sqlite3BtreeRollback: Assertion
`countWriteCursors(pBt)==0' failed.
Aborted
Let me know of anything else. I'll be out for a while today so I'll get to it
tomorrow...
Thanks.
[EMAIL PROTECTED] wrote: Ken wrote:
> Recompiled with:
> gcc -
BEGIN TRANSACTION;
CREATE TEMPORARY TABLE attached_db.temp_table (...);
INSERT INTO attached_db.temp_table SELECT * FROM attached_db.table1;
/* Add a comit */
COMMIT;
DROP TABLE attached_db.table1; -- Error: Table is locked
Yves Goergen <[EMAIL PROTECTED]> wrote: Hi,
I want to modify the st
The segv seems to be resolved. At least no more issues with this version of the
code.
$Id: sqliteInt.h,v 1.606 2007/08/30 14:10:30 drh Exp $
Thanks for a great product.
Ken
Running the same code (sqlitetest_thrd35.c) using shared_cache, occasionally
generates the following output:
Where did the table go?
0 => Executing: COMMIT
3 => Executing: INSERT INTO test_table VALUES(3, 0, 'test3_0')
0 => Executing: select count(*) from test_Table
3 => Executing: INSERT INTO
I did do an update this morning to pick up the latest code base.
I guess the prior version that I had check out earlier in the week was not the
most current.
[EMAIL PROTECTED] wrote: Ken wrote:
> The segv seems to be resolved. At least no more issues
> with this version of th
breakpoints prior to execution.
Ken
Uma Krishnan <[EMAIL PROTECTED]> wrote: Hello I'm trying to debug SQLite (to
understand the code). But e when I attach the process sqlite3, the sqlite3
terminal hangs (ie would not accept any user inputs) till I detach.
Can someone please tell
is there a built in function to display numeric values as hexidecibmal strings?
to_hexstr (40)would display 0x28
Thanks,
Ken
You need to make a copy of the str instead of just capturing a pointer
reference.
try:
my_array[i] = strdup(sqlite3_column_text(pStat, 0));
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: Hello,
I got an error when I try to read some data outside the while{}, inside the
while{} it's ok,
Is there a way for SQLITE to automatically load user defined functions at
database instantiation or upon database connection?
Can it test for a .so/.dll and perform a call to load user functions? If
the .dll does not exist maybe issue a warning?
Just a thought as a way to allow users t
be used to promote user contributions for library
development for sqlite.
For example math function library, or string function library, even the VFS i/o
routines could be loaded in this manner.
Ken
John Stanton <[EMAIL PROTECTED]> wrote: Ken wrote:
> Is there a way for SQLITE to auto
script as an embedded scripting language and another
set which implements a fixed point decimal number type. A wrapper
around sqlite3_open loads them and performs other activities necessary
to cleanly integrate Sqlite into the applications. Sqlite upgrades are
consequently straightforward.
K
4.1/src -shared user_ext.c -o
user_ext.so
Thanks,
Ken
Ken <[EMAIL PROTECTED]> wrote: John very eloquently stated. I completely agree
with you regarding the ant-bloatware philosophy.
OK, I found the answer:
http://www.sqlite.org/cvstrac/wiki?p=LoadableExtensions
Which I'll be
figure the default begin "deffered/immediate/exclusive"
would be nice :)
Ken
Scott Hess <[EMAIL PROTECTED]> wrote: To clarify, this is for Google Gears, a
JavaScript library which
includes a Database component which is implemented using SQLite. If
we were simply building an
oad into sqlite.
Thanks,
Ken
Thomas, if i understand you correctly:
1. Place the writing of multiple rows of data inside a transaction.
2. Querry performance will not be affected by the transaction.
So, If you have multiple rows and are doing something like the following:
1. Begin Transaction
2. Read data from some
Thomas DILIGENT <[EMAIL PROTECTED]> wrote: Hi Ken,
Ken wrote:
> Thomas, if i understand you correctly:
>
> 1. Place the writing of multiple rows of data inside a transaction.
> 2. Querry performance will not be affected by the transaction.
>
> So, If you have mul
od to explore from a performance standpoint.
Regards,
Ken
Joe Wilson <[EMAIL PROTECTED]> wrote: FYI: When this multi-row-insert patch is
combined with today's CVS
OP_Real and OP_Int64 fix for Tickets #2733 and #2731 (Check-in [4507]),
the multi-row ASCII INSERT statements are as much as
oped for simple data unload and reload
Vs the sqlite .dump
Regards,
Ken
Joe Wilson <[EMAIL PROTECTED]> wrote: You're solving a different problem.
Better to stick with the
existing API for what you're proposing.
I just want a faster, more compact and flexible SQL INSERT co
I see now, thanks for the clarification. Sorry for the ramblings.
And there is a .mode csv so that should take care of data loading.
Regards,
Ken
Joe Wilson <[EMAIL PROTECTED]> wrote: --- Ken wrote:
>A new command ".imp" command could be made to use my proposed array
Lee,
1. Qualified Yes, depending on your definition of concurrency.
2. Connections may remain open.
3. Mutexes are not required for protection.
Read the following:
http://sqlite.org/lockingv3.html
Lee Crain <[EMAIL PROTECTED]> wrote: I loosely follow this forum so I am almost
certain this s
If you are using seperate processes then a mutex will not help since it is
local to a process. A semaphore could be used however.
You can use a begin immediate around all statements that perform DML
(ins/upd/sel)
Then loop on the busy at the begin immediate command. This is a fairly simple
thi
.
HTH,
Ken
--- On Sun, 5/3/09, Sam Carleton wrote:
> From: Sam Carleton
> Subject: [sqlite] OT: how best to convert sqlite3_int64 to and from string in
> a cross platform fashion?
> To: "General Discussion of SQLite Database"
> Date: Sunday, May 3, 2009, 4:21 PM
> I am
t; string in a cross platform fashion?
> To: kennethinbox-sql...@yahoo.com, "General Discussion of SQLite Database"
>
> Date: Monday, May 4, 2009, 10:29 AM
> Ken,
>
> this is true, except that I might migrate the system to
> some other database someday that wants to
> On May 4, 2009, at 10:14 PM, Ken wrote:
>
> >
> > You could just pass the sqlite3_int64 value. It is
> portable between
> > systems. Search through the sqlite3 code and there are
> routines that
> > do the conversions from the sqlite3_int64 to a native
Upgrade your ram.
Are you sure its sqlite using all the memory and not the WebServer?
Do you have an index on Events.NotificationTime ?
--- On Tue, 5/5/09, Kalyani Phadke wrote:
> From: Kalyani Phadke
> Subject: [sqlite] Large SQLite3 Database Memory Usage
> To: sqlite-users@sqlite.org
>
ite.org/asyncvfs.html for
> > additional information.
> >
> > This release also includes many small bug fixes and
> documentation
> > improvements.
> >
> > As always, please let me know if you encounter any
> difficulties.
&g
l. I
> need vfs to continue working on
> other databases but to be notified (or have possibility to
> check) when
> one particular database is no longer opened.
>
> Pavel
>
> On Thu, May 7, 2009 at 12:00 PM, Ken
> wrote:
> >
> > --- On Thu, 5/7/09, Vir
ibility with all
> other existing
> VFS implementations.
>
>
> -Original Message-----
> From: sqlite-users-boun...@sqlite.org
> [mailto:sqlite-users-boun...@sqlite.org]
> On Behalf Of Ken
> Sent: quinta-feira, 7 de maio de 2009 13:47
> To: General Discussion of SQLite Dat
not sure really...
But threading in linux will show two processes when a thread is created.
Can you run strace and see if clone is called at thread creation?
Check your threading package and verify its internal operations. Newer versions
do not show duplicate process. But older versions do.
Gene,
Im sure others have suggested, but have you tried running your code through
valgrind?
Can you remove the custom VFS ?
--- On Wed, 5/27/09, Gene Allen wrote:
> From: Gene Allen
> Subject: Re: [sqlite] corrupt database recovery
> To: mgr...@medcom-online.de, "'General Discussion of SQL
Mike,
Not 100% sure of the prior information but a write could slow things down. It
would basically gain the lock to the DB preventing the reads from happening.
But it should not be permanent.
If you are reading all of the data. Could you just execute one query instead of
iterating over all
Also is there an index on the table B.ID field?
--- On Mon, 6/15/09, Mike Borland wrote:
> From: Mike Borland
> Subject: Re: [sqlite] sqlite3_step performance degredation
> To: "General Discussion of SQLite Database"
> Date: Monday, June 15, 2009, 4:11 PM
> Nuno, unfortunately your psychic
>
Along the same lines, the buckets could be created in their own unique Sqlite
Db, thus improving concurrency as well!!!
--- On Thu, 6/25/09, Douglas E. Fajardo wrote:
> From: Douglas E. Fajardo
> Subject: Re: [sqlite] very large SQLite tables
> To: "sqlite-users@sqlite.org"
> Date: Thursday,
This is by design.
The read only transaction acquires a "Read" Lock on the database file.
So if that lock has not been released your writing process will receive the
SQLITE_LOCKED error code.
a. Use a begin exclusive on your writing process and test for sqlite locked.
Using a loop and retry
Seems to me you might need a master and detail tables.
One with the dates, timestamp and one with the data
CREATE TABLE 'log_time' (
id integer primary key
datetimestring VARCHAR COLLATE NOCASE,
timestamp INTEGER,
date INTEGER,
hour INTEGER,
min INTEGER,
sec INTEGER
)
CREATE TABLE 'lo
Ray,
Using multiple threads you will have locking contention on the database. Only
one thread is allowed to write at a time. If you need concurrent writing then
create multiple databases or maybe look into a different DB platform like
mysql, postgress or oracle.
--- On Wed, 7/8/09, Rizzuto,
at case might be
> excessive. Still, it may be worth trying that.
>
> I am using begin/commit around the writes since each order
> can require between 1 and 5 writes.
>
> Ken made a suggestion that I create separate db's for each
> thread. Since the threads don't
be
> worth
> putting begin/commit just around each batch of orders
> instead of each
> individual order. You might want to take it even
> further: by analogy
> with a non-SQL DBMS, I once wrote a logging program which
> did a COMMIT
> only just before a SELECT was needed,
This could then be
copied and written against a target database on a remote server.
Ultimately this would be what rsync provides without the rescans... You could
also look into some form of filesystem replication as well. I think that would
be more reliable.
Just my .02
hth, ken
--- On Sat, 7/18
I like to start each of my transactions with a "Begin Immediate" that way the
database file is locked at that point. And its relatively simple to test for
the DB locked at that stage and handle waiting or returning an error.
HTH
--- On Fri, 7/17/09, Cole wrote:
> From: Cole
> Subject: [sqli
Alex,
I've looked at your code and discussions on this list about the versioning. I
have a few questions.
1. How are you moving the data around from one master to another?
2. How are you applying the changes once moved to the master?
--- On Fri, 7/31/09, Alexey Pechnikov wrote:
> From: Ale
Hi,
I'm getting a Disk I/O error when committing a transaction on an AIX system.
The file system is JFS.
The extended result code is 1290. Which i believe means that the extended code
is a SQLITE_IOERR_DIR_FSYNC error.
Any ideas why this is happening or how to track it down?
Thanks
Thanks Dan!
I'll check this in the morning.
Ken
--- On Tue, 8/4/09, Dan Kennedy wrote:
> From: Dan Kennedy
> Subject: Re: [sqlite] Disk I/O error on AIX
> To: "General Discussion of SQLite Database"
> Date: Tuesday, August 4, 2009, 12:03 AM
>
> On A
Roger,
Thats too funny. I guess I forgot posting this last year.
Ken
--- On Mon, 8/3/09, Roger Binns wrote:
> From: Roger Binns
> Subject: Re: [sqlite] Disk I/O error on AIX
> To: "General Discussion of SQLite Database"
> Date: Monday, August 3, 2009, 7:55 PM
> Ken
ny ideas why this is happening or how to track it
> down?
>
> Compile with SQLITE_DISABLE_DIRSYNC for AIX.
>
> Dan.
>
>
> > Thanks,
> > Ken
> >
Dan, Many thanks. That did the trick!!!
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
--- On Tue, 8/11/09, Radcon Entec wrote:
> From: Radcon Entec
> Subject: [sqlite] Cannot insert records into a table after dropping and
> recreating it
> To: sqlite-users@sqlite.org
> Date: Tuesday, August 11, 2009, 10:50 AM
> Greetings!
>
> I have an application that uses an SQLite database
I'm not sure if this an issue or not. make test failed with the following:
2 errors out of 40872 tests
Failures on these tests: rollback-2.3 tkt3457-1.4
All memory allocations freed - no leaks
Memory used: now 0 max 102680 max-size2800336
Page-cache used: now
--- On Sat, 8/15/09, Dan Kennedy wrote:
> From: Dan Kennedy
> Subject: Re: [sqlite] 3.6.17 test failure
> To: "General Discussion of SQLite Database"
> Date: Saturday, August 15, 2009, 12:36 AM
>
> On Aug 15, 2009, at 2:14 AM, Ken wrote:
>
> > I'
nan-4.16
nan-4.17
Any suggestions or reason why the io test would fail?
io-3.3... Ok
io-4.1...
Expected: [3]
Got: [2]
io-4.2.1... Ok
io-4.2.2... Ok
io-4.2.3...
Expected: [3]
Got: [2]
io-4.3.1... Ok
io-4.3.2... Ok
Thanks,
Ken
___
sqlite-users
CPU Time: user 26.321955 sys 6.498729
sqlite>
Linux:
sqlite> .timer on
sqlite> .output ken.out
sqlite> .read kdo.sql
CPU Time: user 4.648290 sys 0.888056
sqlite>
Thanks,
Ken
Adding pragma temp_store=2 does seem to help, it does red
n for this final select
0|0|TABLE ksrcn WITH INDEX ksrcn ORDER BY
10 seconds for the new vs 14.7 seconds for the original
On linux this same query executes in 5.5 seconds. (After flushing the linux
buffer cache).
Any ideas why this is so slow on aix, where the disk d
> Only problem is
> > there seems to be 1-2s freeze on the moment I create a
> new file.
>
If you are talking about creating a new database periodically with the same
tables: try creating a "template database" and copy that to the new working
version.
The key to increased concurrency is MVCC. Without MVCC concurrency is limited
to page locking, table locking etc.
Google MVCC...
--- On Tue, 9/8/09, Iker Arizmendi wrote:
> From: Iker Arizmendi
> Subject: Re: [sqlite] server process gives better concurrency - why?
> To: sqlite-users@sqlite.o
table might have columns, integer ID and BLOB entity.
But it would be better if you could fully describe the "Entity" internal types
instead of just a var arg...
--- On Thu, 9/10/09, Kavita Raghunathan wrote:
> From: Kavita Raghunathan
> Subject: [sqlite] Question on converting objects into
On additional thing.
One of the indices will not be required. Since one table will be the driving
table and will require a full scan. The other table should have the index. I
would make that the smaller of the tables.
Secondly if at all possible try not to make composit fields. A compoisit fiel
How is the SSD connected? Could it be an issue with the transport layer to the
device?
--- On Mon, 9/21/09, Dave Toll wrote:
> From: Dave Toll
> Subject: Re: [sqlite] SQLite database on a certain high-performance "SSD"
> To: "General Discussion of SQLite Database"
> Date: Monday, September 2
Interesting
Mind if we ask what the SSD device brand and model is?
Is it a disk backed type of device with equal memory in front, I recall seeing
devices like this about 7 years ago. I'm thinking that the sync call is causing
the device to write its memory contents back out to disk (ie to b
--- On Wed, 9/30/09, Scott Hess wrote:
> From: Scott Hess
> Subject: Re: [sqlite] multiple prepare statements
> To: "General Discussion of SQLite Database"
> Date: Wednesday, September 30, 2009, 9:02 AM
> Since SQLite is an embedded database,
> it generally does not pay to
> count statements,
Sql uses a single quote or a tick mark to delimit strings. C, C++ and other
languages use Dobule quote to delimit strings.
I think though that the column names may be double quoted to differentiate them
from data.
--- On Tue, 10/27/09, D. Richard Hipp wrote:
> From: D. Richard Hipp
> Subjec
is mostly insignificant to the speed of disk i/o but every bit
helps...
Just an idea, not sure if its been considered, feasible or even worthwhile.
Ken
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
in case of page
> cache) and good
> > in getting elements by index and traversal of the
> whole list. Last two
> > operations are never executed in SQLite.
> > So looking at all this I don't see how performance can
> be improved
> > (for me it seems that it&#x
k
> something?
I'm not sure it can be improved either. Its just an idea. Implementation and
testing would be the only definitive way to tell.
Agreed that it would degrade performance if the CPU does not have a processor
cache. This alone is reason enough to avoid the ULL for sqlite.
>
point back into the list. So this would be very
problematic for page movement.
Ken
--- On Tue, 10/27/09, John Crenshaw wrote:
> From: John Crenshaw
> Subject: Re: [sqlite] Idea for improving page cache
> To: "General Discussion of SQLite Database"
> Date: Tuesday, Oct
--- On Tue, 11/24/09, Nicolas Rivera wrote:
> From: Nicolas Rivera
> Subject: [sqlite] multiple threads with shared cache mode
> To: sqlite-users@sqlite.org
> Date: Tuesday, November 24, 2009, 12:22 PM
> Hi,
>
> It is my understanding, per
> http://www.hwaci.com/sw/sqlite/sharedcache.html sect
allocate a process wide mutex. Then a semaphor would be simpler.
So in general a mutex is not process capable. Its only when its created
in shared memory that its can be made process wide.
Thanks for raising this point. I've learned something new.
Regards,
Ken
James Dennett <[EMAIL P
Richard Klein <[EMAIL PROTECTED]> wrote: Dan Kennedy wrote:
> On Wed, 2007-10-24 at 21:38 -0700, Richard Klein wrote:
>> As I was thinking about the locking mechanism in SQLite 3,
>> it occurred to me that the following race condition could
>> occur.
>>
>> Imagine a joint bank account with a bala
(journaled/ordered), etc..
Maybe you have different filesystems. What about raid devices?
Ken
Fabio Durieux Lopes <[EMAIL PROTECTED]> wrote: Hmm, GW0 (RHE3, the fast one)
does 190-300 inserts/second. GW2 does
around 15 inserts/second.
I'm gonna try to commit every 1000 records and I'
you may set a transaction to
serailazable as well.
Sorry for my confusion and thanks for the clarification.
Ken
Ken wrote:
>
> BEGIN TRANSACTION;
> SELECT balance FROM accounts WHERE accountId = '123-45-6789';
> UPDATE accounts SET balance =
>
restarted. The select would be run again, returning process B's correct value
of (10,000 + 1000) = 11,000 ;
A simpler/cleaner implementation might be:
begin immediate --- Busy waiting would occur here. ie sqlite busy is
returned.
select
update
commit;
Ken
Ken &l
urning SQLITE_IOERR)?
Thanks,
- Richard Klein
[EMAIL PROTECTED] wrote:
> Ken wrote:
>> BEGIN TRANSACTION;
>> SELECT balance FROM accounts WHERE accountId = '123-45-6789';
>> UPDATE accounts SET balance =
>> WHERE accountId = '123-45-67
Free.
http://www.cs.umass.edu/~emery/hoard/screenshot.html
http://www.garret.ru/~knizhnik/threadalloc/readme.html
Regards,
Ken
ge in direction and philosophy.
Regards,
Ken
[EMAIL PROTECTED] wrote: "Dan Petitt" wrote:
> Richard, i noticed this ticket in the system:
> http://www.sqlite.org/cvstrac/tktview?tn=2417,8
>
> And wondered if its something that is getting any serious thought or
>
Dan,
The journal file contains the "before" image of a modified database block not
the after image.
during write operations: before images are written to the journal file for
recovery.
Then the actual change is written to the .db file.
A commit is an atomic operation due to unlinking the j
In order to maximize compatibility between SQLite and other database engines,
SQLite support the concept of "type affinity" on columns. The type affinity of
a column is the recommended type for data stored in that column. The key here
is that the type is recommended, not required. Any column
Per your wiki link:
Q) How can the strict affinity mode be used which is claimed to exist on
http://www.sqlite.org/datatype3.html A) This has not been implemented as of
version 3.3.13.
Jarl Friis <[EMAIL PROTECTED]> wrote: "Trevor Talbot" writes:
> On 11/4/07, K
I think your blob file performance may greatly depend upon the file system that
it used and the workload.
I found this article:
http://oss.sgi.com/projects/xfs/papers/filesystem-perf-tm.pdf
Andreas Volz <[EMAIL PROTECTED]> wrote: Am Tue, 13 Nov 2007 07:18:19 -0600
schrieb John Stanton:
> In
ccurred requiring thread shutdown ?
In general I'v found that Thread cancellation is very painful, a simpler
paradigm to utilize is the lock timeout with a Global variable status check.
I'm really looking forward to DRH's work on memory Management model.
Regards,
Ken
Joe Wilson <
Some suggestions:
Under the SQL Language page, Split the page "expressions" into two, one
for the sql expressions and one for SQL functions. It was not immediately
obvious what sql functions were supported nor where to find them.
Spelling/Grammar Home Page: second to last paragraph
ES(1,5);
COMMIT;
select * from chain where ( a=2 and (b&8) and !(b&4)) ;
SQL error: unrecognized token: "!("
SQLite documentation indicates that "!" is a unary prefix operator. Is this a
bug?
Vs:
sqlite> select * from chain where ( a=2 and (b&8) and not (b&4)) ;
a|b
2|8
Regards,
Ken
ct by prior, What if at
all possible would be the syntax for sqlite?
Thanks,
Ken
101 - 200 of 592 matches
Mail list logo
