Kurt Welgehausen wrote:
>> ... only the first index is opened ...
>
> That's right. SQLite uses only one index, and it doesn't keep
> statistics, so it may pick the wrong index if it has to choose.
> Try forcing it to use the other index by dropping the one that
> it's using now.
>
> Changing
Thank you for that Miguel, but this is not good.
DRH, if we don't get the type information returned for Views, what is
the point of getting it back for SELECTs? Views are completely useless
to SQLite users who rely on the type information to interpret the result
sets. Is this something you
Read the documentation:
"The first parameter is a prepared SQL statement. If this statement is a
SELECT statement, the Nth column of the returned result set of the SELECT is
a table column then the declared type of the table column is returned. If
the Nth column of the result set is not at table
Can someone please please answer the question, does
sqlite3_column_decltype NOT return the column type for Views? I don't
see how this wouldn't considered as a major bug.
EzTools Support wrote:
I found out why Views were returning all NULLs. I have made a
modified version of sqlite3_exec.
Jakub Adamek, dando pulos de alegria, escreveu :
That's GREAT ! Nuno, are you going to merge Sqlite-Wince STABLE ?
I'll do that during this week.
Regards,
~Nuno Lucas
Monday, September 20, 2004, 5:11:48 AM, Mike wrote:
> this file is incomplete, and has been for some time. here is the correct
> version. would somebody check it in, since I dont have CVS access handy:
The only additional symbol I see is sqlite3_version which is not a
function. The
Hi,
I'm not sure whether it's a problem with my english or the SQLite code.
SQLite in version 2 and 3 knows several macros which defined or not add
or remove certain functionalities to eventually reduce the memory
footprint of the SQLite library.
SQLiteInt.h introduces:
/*
** When building
I found out why Views were returning all NULLs. I have made a modified
version of sqlite3_exec. Mine checks for NULL returned from
sqlite3_column_decltype, for which Sqlite3 now returns NULL. Am I right
that this is so? My COM wrapper depends on having the column data types
returned for
this file is incomplete, and has been for some time. here is the correct
version.
would somebody check it in, since I dont have CVS access handy:
EXPORTS
sqlite3_aggregate_context
sqlite3_aggregate_count
sqlite3_bind_blob
sqlite3_bind_double
sqlite3_bind_int
sqlite3_bind_int64
sqlite3_bind_null
alessandro bonvicini wrote:
Hi all, I ask you an help because I don't understand what I am doing
wrong with sqlite.
First of all,anyway, I would like to thanks all of you for this software.
Now I have some problem but I only need to understand where are my
errors and I am sure that sqlite will
Hi all, I ask you an help because I don't understand what I am doing wrong
with sqlite.
First of all,anyway, I would like to thanks all of you for this software.
Now I have some problem but I only need to understand where are my errors
and I am sure that sqlite will be as fast as everyone says.
11 matches
Mail list logo
