Mrs. Brisby wrote:
> My PII-350 easily handles 2 million local deliveries per hour, and it
> fork()s for each one.
>
> As has been mentioned: If you think threads are going to make your
> program fast, you don't know what you're doing.
Like it or not, the world is bigger than just Unix. Some of
>notice the uppercase F from Field1, although field1 is requested.
>So, it seems that sqlite returns column names as defined in schema, not as
>requested by the user. This may not seem a big problem, but it becomes one
>when working with columns and trying to refer them by name and not wanting
That's a good question. It would save all the wrapper writers some
time. I don't think the library is the place to put thread safe
code for several reasons:
Some of us don't use threads and don't need thread
safe code.
I prefer modular code with as little mixing of function
as possible. It makes
Jay wrote:
The begin and end functions could be configured
to begin/end the transaction *if* there isn't/is
one.
Dumb idea?
Do I get get to wear the dunce hat? :)
You should really look at an object oriented language.
You can do exactly this very simply.
But why should he have to? This
Andrew Piskorski wrote:
On Thu, Mar 17, 2005 at 08:33:03PM -0700, Ara.T.Howard wrote:
On Sat, 12 Mar 2005, Andrew Piskorski wrote:
On Sat, Mar 12, 2005 at 10:03:25AM -0700, Ara.T.Howard wrote:
does anyone have a strategy for doing massive updates to a db and atomicly
replacing it in
le, either because I didn't open a
ticket for it or because
my example wasn't as nice, compact, and obvious as the one on Ticket 1159).
--
Eli Burke
I've been working on a project using sqlite3 since last fall. At the time,
I knew that it would need a web-based front-end eventually. I have a very
small bit of experience with PHP, and I assumed that PHP would support
sqlite3 sooner or later. Well, it's later, and as far as I know, PHP
is still
D. Richard Hipp wrote:
This released is labeled "alpha" but it is still very well
tested. By being "alpha" it means that there is still a
small window of opportunity during when users can suggest
API changes. Once we go to beta (in about a week) no more
changes will be accepted. So if you want
2. disable asserts. I don't know how this is done in C, but I assume
that in
a release build, asserts are off.
Disable asserts() using -DNDEBUG=1. This more than doubles the speed
of SQLite. Asserts() are turned off in release builds.
We build sqlite3.08 as follows: ./configure
Paul Dixon wrote:
I'm having some problems with multi-threaded updates failing.
Multiple threads open their own sqlite connection with sqlite3_open()
and then call sqlite3_busy_timeout(handle, 3) to give a 30 second
timeout. These threads then perform some inserts on the same table, but
I get
(1) Form of wildcards:
?
?N
:N:
$N
At various places in the documentation, all of these seem to be
mentioned, though not all consistently. At times N is only a numeric
integer, while at others it is a fully alphanumeric identifier. The
last ($) form, is hinted at only in the header file,
I've read through pretty much everything available on sqlite.org,
including Dr. Hipp's helpful slides from
the 2004 International PHP conference (slides 56-58), but I still feel
like I'm stumbling around in the dark
when it comes to writing optimizedl SQL queries (specifically, SELECTS +
The configure script makes .libs/libsqlite3.a for me, without
arguments or fiddling.
I use
../sqlite/configure --enable-threadsafe
to build the threadsafe, no tcl, and as a static lib version.
Can you tell me what fiddling you did to "fix" it?
Ok, color me embarassed. I rebuild again from
I may be in a minority here, but I needed to build sqlite3: threadsafe,
no tcl, and as a static lib.
With both 3.06 and 3.08, this required fiddling as the configure script
does not create libsqlite3.a.
configure --help does report:
--enable-static[=PKGS] build
14 matches
Mail list logo
