On 9/16/17, David Wellman wrote:
> Hi,
>
> If you download the 3.20.1 documentation zip file from
> http://www.sqlite.org/download.html the pages still show as 'Draft' (in big
> red letters).
>
> Not a major issue but it is a bit disconcerting when you first see it.
The documentation build proble
On 9/16/17, David Wellman wrote:
>
> Q1) I believe that the "sqlite3_prepare_v2" function parses the sql text to
> check it is valid, the named objects exist etc. and builds the 'executable
> program'. Does this function run the SQL? I don't think so.
>
sqlite3_prepare_v2() does not run your SQL.
Hi,
If you download the 3.20.1 documentation zip file from
http://www.sqlite.org/download.html the pages still show as 'Draft' (in big
red letters).
Not a major issue but it is a bit disconcerting when you first see it.
Cheers,
Dave
Ward Analytics Ltd - information in motion
Tel: +44 (0) 1
Hi,
I'm just trying to check my understanding of what happens when running a
query against SQLite and particularly how that might affect interaction
between an application and SQLite.
The SQL itself isn't really important for now, but assume it's a select
statement which will return some da
On 2017-09-16 12:37 PM, Richard Hipp wrote:
On 9/16/17, Jens Alfke wrote:
On Sep 15, 2017, at 11:40 PM, Wout Mertens wrote:
This would be handy when specifying `INSERT INTO t(@?) VALUES(@?)` or
`SELECT
* FROM t WHERE v IN (@?)`.
I'm definitely not an expert on the SQLite virtual machine,
On 2017-09-16 12:01 PM, Jens Alfke wrote:
On Sep 15, 2017, at 11:40 PM, Wout Mertens wrote:
This would be handy when specifying `INSERT INTO t(@?) VALUES(@?)` or `SELECT
* FROM t WHERE v IN (@?)`.
I'm definitely not an expert on the SQLite virtual machine, but I believe that
changing these p
On 9/16/17, Jens Alfke wrote:
>
>
>> On Sep 15, 2017, at 11:40 PM, Wout Mertens wrote:
>>
>> This would be handy when specifying `INSERT INTO t(@?) VALUES(@?)` or
>> `SELECT
>> * FROM t WHERE v IN (@?)`.
>
> I'm definitely not an expert on the SQLite virtual machine, but I believe
> that changing
> On Sep 15, 2017, at 11:40 PM, Wout Mertens wrote:
>
> This would be handy when specifying `INSERT INTO t(@?) VALUES(@?)` or `SELECT
> * FROM t WHERE v IN (@?)`.
I'm definitely not an expert on the SQLite virtual machine, but I believe that
changing these parameters [or at least the number o
that is perfect.
Thanks, Clemens!
Regards.
Brian P Curley
On Sat, Sep 16, 2017 at 5:14 AM, Clemens Ladisch wrote:
> Brian Curley wrote:
> > WITH cte_name --(my_row, code_key)
> > AS (
> >SELECT-- Base record
> >
Oh right, didn't really think about that one. What about binding the array
though, maybe a bind_array call that specifies that a given parameter will
be an array, and then push elements with the regular bind calls?
On Sat, Sep 16, 2017 at 8:51 AM Darren Duncan
wrote:
> I agree that being able to
Brian Curley wrote:
> WITH cte_name --(my_row, code_key)
> AS (
>SELECT-- Base record
> 1my_row
> ,(SELECT
>max(code_key)
> FROM
>
11 matches
Mail list logo