Re: svn commit: r1383480 - in /subversion/trunk/subversion: svn/cl.h svn/log-cmd.c svn/main.c tests/cmdline/getopt_tests_data/svn_help_log_switch_stdout tests/cmdline/log_tests.py

On Fri, Sep 21, 2012 at 06:00:08AM -0700, C. Michael Pilato wrote:
> On 09/21/2012 04:34 AM, Branko Čibej wrote:
> > How about having just the --search option and creating a simple query
> > language parser using parenthesis, AND, NOT and OR operators? I'd even
> > consider making such searching always case-insensitive, at least for log
> > messages; alternatively, the query language could have a CI operator
> > that made the associated subquery case-insensitive (and the obverse CS
> > operator).
>
> These was my same immediate first thoughts upon seeing the suggestion of
> --search-and, too. But yeah, not planning to invest any time here myself.

And this idea was also discussed on IRC back in June:
http://colabti.org/irclogger/irclogger_log/svn-dev?date=2012-06-28#l169

What I took away from that discussion was that going down this route
has a lot of potential to get out of hand rather quickly :)

<peterS> people will then expect magic quoting as in search engines. 'foo bar' would have an explicit AND or OR (your choice) but ' "foo bar" ' would not
<peterS> oh yeah and people will expect ( ) to work
<peterS> and then, at some point, somebody will want SQL WHERE clause syntax

<stsp> yes, and then we might as well just cache all this stuff in an sqlite db and allow people use sql in the --search argument

<peterS> svn log --search "author LIKE 'phil%' AND date BETWEEN '2012-01-05' AND '2012-01-08'"
Received on 2012-09-21 16:18:21 CEST