Does any one know of a way to know which columns are to be used in a virtual
table implementation for a particular query? At the xFilter() point the engine
essentially knows what it is going to do and what columns it will use, but that
information does not seem to be exposed anywhere. Certainly I know some of the
columns used for the constraints, but I do not know all of them nor do I know
all those required for processing the query.
I can get significant improvement if I do not have to provide all possible
columns for a row when I only need a few.
Thanks,
-Allan
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
