[
https://issues.apache.org/jira/browse/SVN-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749201#comment-16749201
]
Branko Čibej edited comment on SVN-4804 at 1/23/19 3:28 AM:
------------------------------------------------------------
Here's what happens: with this option enabled, the output of {{EXPLAIN QUERY
PLAN}} for statements like {{STMT_FINALIZE_UPDATE_MOVE}}, which are just
(conditional) {{DROP TABLE}} statements, contains output like the following:
{noformat}
SCAN TABLE sqlite_master
{noformat}
and no further details. Later on, {{test_query_expectations}} complains that
the query is not using an index — but {{sqlite_master}} doesn't _have_ an
index, so this warning (which is returned as an error from the test case) is
bogus.
was (Author: brane):
Enabling this option causes the {{test_query_expectations}} test case to parse
SQLite's {{EXPLAIN QUERY PLAN}} output, but our parser is out of date and
fails, causing the test itself to fail.
> wc-queries-tests fail with SQLite's profiling enabled
> -----------------------------------------------------
>
> Key: SVN-4804
> URL: https://issues.apache.org/jira/browse/SVN-4804
> Project: Subversion
> Issue Type: Improvement
> Components: libsvn_wc
> Affects Versions: all
> Reporter: Branko Čibej
> Assignee: Branko Čibej
> Priority: Major
>
> See: [https://bugs.gentoo.org/605438].
> Adding {{-DSQLITE_ENABLE_STMT_SCANSTATUS}} to {{CPPFLAGS}} causes on of the
> {{wc-query-tests]} to fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
