> Dominique Devienne wrote: > > An alternative is to expose a virtual table with a fixed set of rows, and > accepting updates on the values, which can also then be "typed" too. > But that's a lot more complicated though. > (and refusing inserts/deletes too, of course). > > That vtable could also expose version information for the extension, for > example, and those would be read-only. Just thinking aloud. > Avoids non-deterministic functions.
A vtable with a fixed number of rows, one for each config parameter - this approach sounds interesting. I'll have to investigate how complicated it will be to implement such an approach. Regards, Ulrich _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
