On Thu, Aug 27, 2015 at 1:08 PM, Richard Hipp <drh at sqlite.org> wrote:
> On 8/27/15, Dominique Devienne <ddevienne at gmail.com> wrote: > > > > I understand that https://www.sqlite.org/opcode.html doesn't explicitly > say > > what VOpen's p4 column will contain, so I guess one could argue this is > > undocumented behavior we should not rely on, .... > > On needn't argue this; it is explicitly stated in the EXPLAIN > documentation (https://www.sqlite.org/lang_explain.html): > > "The output from EXPLAIN and EXPLAIN QUERY PLAN is intended for > interactive analysis and troubleshooting only. The details of the > output format are subject to change from one release of SQLite to the > next. Applications should not use EXPLAIN or EXPLAIN QUERY PLAN since > their exact behavior is variable and only partially documented." > OK. Right you are of course. Thank you for pointing this out for me. I did that a long time ago, and probably didn't notice this disclaimer (I assume it was already there back then). That does not remove though the need for our application to do this kind of introspection. How then do you recommend we go about this? I.e. how can we programatically reliably discover which (v)tables a view accesses, staying in documented behavior land? Thanks, --DD PS: FWIW, I'm still curious why change took place. I could do a "blame" if I was Fossil-savvy, but even then I'm not sure I'd get it from the diff.
