Another possibility might be to create a parameters table, say: CREATE TABLE tabparams (p1,p2,p2,p4,p5); INSERT INTO tabparams VALUES (null,null,null,null,null);
And when creating the view, access tabparams.p1, tabparams.p2, etc. instead of variables (with an appropriate join clause). Then, before accessing the view, update the tabparams table with the values you want. This may be more expensive, depending on the optimizer, since SQLite will no longer be dealing with a constant but rather a join. A more elaborate method would be to program a pair of parameter_set and parameter_get functions in C. Integer parameter_set (integer parameter_no, value pvalue) Value parameter_get (integer parameter_no) The parameter values would actually be stored during the session in the application data for the sqlite3_create_function_v2 function, and deleted at the session end by the destroy function you pass to it. This has the possible advantage that I think functions with constant arguments are treated themselves as constants. This has the disadvantage that software that didn't load your functions would not be able to access the views at all. Best regards, Peter _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
