*context, int argc, sqlite3_value
**argv){
double rVal=0.0;
- i64 iVal=0;
assert( argc==1 );
switch( sqlite3_value_type(argv[0]) ){
case SQLITE_INTEGER: {
--
Seth Falcon | @sfalcon | http://userprimary.net/
___
sqlite-users mailing list
sqlite
Hi,
I've integrated the extension-functions.c code into an R package so that
these functions can be used in R via RSQLite. In the process, I came
across a couple of compiler warnings that seemed to have easy fixes. I
could not find contact information for Liam Healy so am posting this here.
[EMAIL PROTECTED] writes:
> Please forgive me, because I know this has been covered before, but
> at the moment I'm at a loss. I am writing an SQLite wrapper for a
> relatively new language, and one of the requirements is that the
> user be able to add and update date as if they were using an
Joe Wilson <[EMAIL PROTECTED]> writes:
> This is the internal code that sqlite uses to convert the
> declaration type to the REAL, INT, TEXT, BLOB types.
>
> Happy hacking...
Thanks for the pointer. I can create the appropriate struct and call
sqlite3AffinityType and this gives me a solution.
Hi all,
Is there a way to obtain the SQLite type (e.g. SQLITE_INTEGER) given
the declared type from the schema?
What I'm really trying to do:
I'm working on RSQLite, an interface for the R language to SQLite.
I want to determine the type of the columns in an arbitrary result
set.
"Igor Tandetnik" <[EMAIL PROTECTED]> writes:
> This is not unusual when you index a field with low cardinality
> (number of distinct values). To illustrate, imagine that allele=0 in
> all rows. A simple scan without using an index would look once at each
> row, for a complexity of O(N) (where N is
Hi all,
I'm working with a table with ~3 million rows and 7 columns.
Recently, I found that a simple query takes longer _after_ adding an
index. I find this surprising. Can someone provide some insight?
Here are some details:
The schema:
CREATE TABLE pmfeature (
fid integer not
7 matches
Mail list logo