I think I prefer something along the lines of "unlikely" or "likely". The
problem with a term like "selective" (at least in my brain) is that it
doesn't imply (for the single argument version) in what way it is being
selective.
If a negative form of the magic function is used ("unlikely", "seldom",
etc) I would suggest considering inverting the optional second parameter.
In other words, 0.05 would become 0.95. In my opinion, that reads better:
"unlikely(COLUMN LIKE '%pattern%', 0.95)" reads "it is unlikely the
expression will be true 95% of the time".
In like fashion, a positive form of the magic function would keep the
current meaning of the optional second parameter.
Just ideas, I'm not married to them. Thanks for the discussion.
SDR
On Tue, Sep 10, 2013 at 4:17 PM, Eric Minbiole <eminbi...@gmail.com> wrote:
> > (1) unlikely(EXPR)
> > (2) selective(EXPR)
> > (3) seldom(EXPR)
> > (4) seldom_true(EXPR)
> > (5) usually_not_true(EXPR)
> >
> >
> I quite like (2) "selective". I think it's reasonably descriptive on its
> own, and also works well with the optional second argument.
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
