RE: [sqlite] Quick question about sqlite_trace

For every statement; great! --Keith -Original Message- From: Keith Herold [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 13, 2004 11:03 AM To: [EMAIL PROTECTED] Subject: [sqlite] Quick question about sqlite_trace Does sqlite_trace fire for every sql statement in a sql_exec, or

Re: [sqlite] strange rounding problem

Donald, Will Leshner <[EMAIL PROTECTED]> 14/10/2004 04:20 AM Please respond to sqlite-users To: [EMAIL PROTECTED] cc: Subject:Re: [sqlite] strange rounding problem >The point is that the number is in the database as '358', but by the time we get it

Re: [sqlite] strange rounding problem

[EMAIL PROTECTED] wrote: Can you come up with a minimal test case that exhibits this behaviour? Ideally, it would be a series of SQL statements written into the sqlite shell program that results in something visibly wrong. The second best case would be a short (10-20 line) C program that uses

RE: [sqlite] sqlite with Borland C++ 5.02

Excellent. Thanks. -Original Message- From: Dennis Cote [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 13, 2004 3:03 PM To: [EMAIL PROTECTED] Subject: Re: [sqlite] sqlite with Borland C++ 5.02 Pigott, Paul wrote: > Is there a pre-compiled binary for that? Or do you just convert

Re: [sqlite] sqlite with Borland C++ 5.02

Pigott, Paul wrote: > Is there a pre-compiled binary for that? Or do you just convert the > .DLL to a .LIB with a utility? You need to generate an Borland import library for the DLL using Borland's IMPLIB utility. The command to use depends upon which version of sqlite you are using. For SQLite

Re: [sqlite] strange rounding problem

Griggs, Donald wrote: If I'm missing the (decimal) point, here, forgive me. The point is that the number is in the database as '358', but by the time we get it back from a query it has become '357.999'. We aren't doing any floating point with the number. It is (apparently) happening for us in the

[sqlite] Quick question about sqlite_trace

Does sqlite_trace fire for every sql statement in a sql_exec, or just for the whole sql_exec/sql_compile? I.e., suppose the call to sql_exec is: BEGIN TRANSACTION; INSERT INTO tblMyDestinationTable (Dogs, Cats, FoodCosts) SELECT * FROM tblMyTable tmt WHERE tmt.Foo = 'bar'; SELECT

Re: [sqlite] strange rounding problem

Will Leshner wrote: I've tracked my rounding problem down to this line in vxprintf(): I'm sorry to say that is a false alarm. It turns out that we were being fooled by the debugger in Dev Studio. What is the case, however, is that a value is coming out of the database and at some point duing the

Re: [sqlite] DBD::SQLite2 installation on Debian

At 3:56 PM +0100 10/13/04, Slava Bizyayev wrote: I have strange results with sqlite-2.8.15. For some unclear for me reason I can not write to database via the dbish or DBI (DBD::SQLite2). I guess I'm doing something wrong, but I have no idea what exactly... [EMAIL PROTECTED]:~$ dbish

Re: [sqlite] sqlite with Borland C++ 5.02

Pigott, Paul wrote: Is there a pre-compiled binary for that? Or do you just convert the .DLL to a .LIB with a utility? Paul -Original Message- From: nfr [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 13, 2004 12:21 PM To: [EMAIL PROTECTED] Subject: Re: [sqlite] sqlite with Borland C++

RE: [sqlite] sqlite with Borland C++ 5.02

Is there a pre-compiled binary for that? Or do you just convert the .DLL to a .LIB with a utility? Paul -Original Message- From: nfr [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 13, 2004 12:21 PM To: [EMAIL PROTECTED] Subject: Re: [sqlite] sqlite with Borland C++ 5.02 Pigott,

Re: [sqlite] sqlite with Borland C++ 5.02

Pigott, Paul wrote: Greetings, I'm new to sqlite. I'm trying to get it setup to work with the Borland C++ 5.02 compiler. I've keyed in the sample program at http://www.sqlite.org/quickstart.html and I keep getting "unresolved externals" for _sqlite3_open,

Re: [sqlite] LIKE, BETWEEN

This is very strange. Common sense will tell us that a BETWEEN call on the "a" column should use the index "t_idx_0". I can't see why SQLite is doing a table scan. Is this another one of those code-optimized features of SQLite to forget intelligent parsing and processing in order to reduce DLL

[sqlite] LIKE, BETWEEN

In sqlite3 queries using LIKE and BETWEEN do not use existing indices. So for a schema like CREATE TABLE t (a integer, b char(40)); CREATE INDEX t_idx_0 ON t(a); CREATE INDEX t_idx_1 ON t(b); queries like "SELECT * FROM t WHERE a BETWEEN 1 AND 20"or "SELECT * FROM t WHERE b LIKE 'abc%'" end