On 2014/03/05 17:05, Chris wrote:
Ok, fair enough. I thought that in the same way that sqlite looks for
binary vs. string representations of referenced vars and has alternative
ways of specifying variable to bind to ('@', ':'), it might also spot a
list object and internally expand it to
> On Wed, Mar 5, 2014 at 4:59 AM, Chris wrote:
>
> > I'm a relative novice to sqlite (or sql in general), but I do understand
> > the value of variable substitution when building queries:
> >
> > e.g.
> > set someValue 23
> > db eval {SELECT something FROM myTable WHERE value=$someValue}
On Wed, Mar 5, 2014 at 4:59 AM, Chris wrote:
> I'm a relative novice to sqlite (or sql in general), but I do understand
> the value of variable substitution when building queries:
>
> e.g.
> set someValue 23
> db eval {SELECT something FROM myTable WHERE
On Wed, Mar 5, 2014, at 09:59 AM, Chris wrote:
> I'm a relative novice to sqlite (or sql in general), but I do understand
> the value of variable substitution when building queries:
>
> e.g.
> set someValue 23
> db eval {SELECT something FROM myTable WHERE value=$someValue}
>
> It feels
I'm a relative novice to sqlite (or sql in general), but I do understand
the value of variable substitution when building queries:
e.g.
set someValue 23
db eval {SELECT something FROM myTable WHERE value=$someValue}
It feels like there should be a comparable solution for IN, passing
5 matches
Mail list logo