At 12:49 AM +0100 9/12/04, Matt Sergeant wrote:
This is just because Mac OSX is fussy - Linux won't complain and will let
the latterly loaded symbol supercede. But it's a valid bug in
DBD::SQLite2, so I'll fix it in the next release (should be simple).
Matt.
Now, unless you have a Mac OS X box of
On Sat, 11 Sep 2004, Darren Duncan wrote:
> And the results:
>
> [S0106000393c33758:Documents/Perl Distributions/devworld]
> darrenduncan% ../perl58 dbd_load_test.pl
> dyld: ../perl58 multiple definitions of symbol _sqlite_busy_timeout
>
On Sat, 11 Sep 2004, Darren Duncan wrote:
> However, this SQLite v2 and SQLite v3 can not be used simultaneously
> as they have symbol conflicts. The one flagged was
> _sqlite_busy_timeout, but from a quick scan of the offending files
> there seem to be more conflicts. It all looks like a
At 4:05 PM -0700 9/11/04, Scott Leighton wrote:
I'm not seeing any such problem here. The following code works
perfectly with DBD::SQLite2 v0.33 and DBD::SQLite v1.05.
You don't 'use' the DBD modules, you use DBI; and it handles loading
of the modules specified in the connect.
Scott
I know
On Saturday 11 September 2004 3:19 pm, Darren Duncan wrote:
> Just now I installed the newest versions of DBD::SQLite v1.05 (3.06)
> and DBD::SQLite2 v0.33 (2.8.15). They both tested and installed with
> no problems, along with DBI v1.43 and Perl v5.8.5, all using GCC 3.3
> on Mac OS X 10.2.8.
>
Just now I installed the newest versions of DBD::SQLite v1.05 (3.06)
and DBD::SQLite2 v0.33 (2.8.15). They both tested and installed with
no problems, along with DBI v1.43 and Perl v5.8.5, all using GCC 3.3
on Mac OS X 10.2.8.
However, this SQLite v2 and SQLite v3 can not be used
On Fri, 10 Sep 2004 15:58:24 -0400, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
OK. My workaround trick didn't work afterall. Looks like you
are stuck with a temporary file when doing an UPDATE or a mass
INSERT inside a transaction.
yes. update may be very simple. See the following log:
SQLite
Ed Porter wrote:
I found that performance began to fail miserably as the blob size increased
above 500 bytes (has anyone else experienced this problem?).
I just ran a test where I do "count" INSERTs of a BLOB of different sizes.
Here's the result:
size=100 count=100 time=26374 microseconds per
On Fri, 10 Sep 2004, Darren Duncan wrote:
> With this round, I will start using the new stuff like named host parameters.
Sadly named host params are still broken in sqlite 3.0.6. When I parse
this SQL:
SELECT user_id, fname, lname FROM users
WHERE lname like :1
UNION
SELECT user_id,
Vladimir Vukicevic, dando pulos de alegria, escreveu :
Hi yesso,
On Sat, 11 Sep 2004 09:02:08 +0200, yesso <[EMAIL PROTECTED]> wrote:
hi, can i use this provider in a c# project?
Yes, you can use it with any language that can access ADO and/or OLE-DB
databases.
But as Vladimir pointed out, you
Hi yesso,
On Sat, 11 Sep 2004 09:02:08 +0200, yesso <[EMAIL PROTECTED]> wrote:
>
> hi, can i use this provider in a c# project?
>
You may want to also look at the SQLite ADO.NET provider at
http://www.mono-project.com/contributing/sqlite.html , which is part
of mono's class libraries, but
HI there!
I have just migrated to my application from hsqldb to SQLite-2.8 using
the jdbc-driver from christian werner.
However I have a problem with the following statement which is used very
oftern to increment indexes.
I know this is not a cool way to archieve this, however I must be 100%
fully
Hi Ken
I found that performance began to fail miserably as the blob size increased
above 500 bytes (has anyone else experienced this problem?). When I posted
the problem, I think that someone stated the docs show the reasonable limit
on blobs is 230 bytes. Anyways, I had to store the blobs direct
13 matches
Mail list logo
