Hi…
I'm new to this mailing-list because I have a problem to define a
"VIRTUAL TABLE"
sqlite3 extension. I already have a working implementation with close empty
*xBestIndex and *xFilter.
1) My data is already in a sorted list with ONE or MORE primary index
columns
2) Currently the VTAB is always doing a FULL TABLE SCAN even for trivial
search.
3) my schema define in sqlite3_declare_vtab is
"CREATE TABLE %s ( \
rep VARCHAR(3), \
par VARCHAR(3), \
year INTEGER, \
imp DOUBLE, \
exp DOUBLE, \
PRIMARY KEY(rep,par,year) \
)"
4) it seems that sqlite does NOT use the "PRIMARY KEY(rep,par,year)"
information…
5) the key data is already sorted…
6) I expect for a primitive WHERE clause like "rep=XXX" some kind of access
optimization…
I'm looking for a "starter" implementation with the conditions from above
with working *xBestIndex and *xFilter…
Thanks for your help.
mfg ao
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
