On 2015-09-19 06:41 PM, gwenn wrote:
> SQLITE_SCHEMA is returned only on failure.
> But, here, there is not failure.
>
> Maybe I should not store the column count ?
> Maybe I should look at schema version
> (http://sqlite.org/pragma.html#pragma_schema_version):
> "The schema version is used by
On 19 Sep 2015, at 5:41pm, gwenn wrote:
> Is there a better solution ?
Why do you want to know when the statement has been recompiled while you're in
the middle of processing a SELECT command ? Are you doing something that might
make you pause for a long time before executing your last
SQLITE_SCHEMA is returned only on failure.
But, here, there is not failure.
Maybe I should not store the column count ?
Maybe I should look at schema version
(http://sqlite.org/pragma.html#pragma_schema_version):
"The schema version is used by SQLite each time a query is executed to
ensure that
On Sat, 19 Sep 2015 11:29:37 +0200, gwenn
wrote:
>Hello,
>Is there any way to know when a prepared statement is recompiled ?
>For example:
>
>rc = sqlite3_prepare_v2(db, "SELECT * FROM test", -1, , NULL);
>...
>cc = sqlite3_column_count(stmt);
>...
>rc = sqlite3_exec(db, "ALTER TABLE test ADD
Hi gwenn,
Maybe you are talking about something I don't understand, or I don't understand
what you are
talking about...
I would like somebody tells if I'm wrong or right,
first in your email you have both :
> >>rc = sqlite3_prepare_v2(db, "SELECT * FROM test", -1, , NULL);
> >>...
> >>...
>
Em 19/09/2015 11:13, "Rob Willett" <
mail.robertwillett.com at postfix.robertwillett.com> escreveu:
>
> Ryan,
>
> Thanks. We?ve got 100 requests a second which may be enough. We?ll keep
looking though for any time.
>
Have you considered to implement the service using a compiled language,
Ryan,
Thanks. We?ve got 100 requests a second which may be enough. We?ll keep looking
though for any time.
Rob.
> On 18 Sep 2015, at 18:26, R.Smith wrote:
>
> >>>Rob: "We want to do postal code ==> GPS..."
>
> >>Me: "You can use google apis..."
>
> >Rob: "Our business is GPS and GIS
Hello,
Is there any way to know when a prepared statement is recompiled ?
For example:
rc = sqlite3_prepare_v2(db, "SELECT * FROM test", -1, , NULL);
...
cc = sqlite3_column_count(stmt);
...
rc = sqlite3_exec(db, "ALTER TABLE test ADD COLUMN data DEFAULT
'missing'", NULL, NULL, NULL);
...
rc =
Maybe I should have sent a patch:
diff src/sqlite.h.in.bak src/sqlite.h.in
3629c3629
< ** [sqlite3_bind_parameter_index()].
---
> ** [sqlite3_bind_parameter_name()].
Regards.
On Tue, Aug 4, 2015 at 8:14 PM, gwenn wrote:
> Hi,
> In the following page:
>
On 19 Sep 2015, at 9:46am, gwenn wrote:
> Maybe I should have sent a patch:
>
> diff src/sqlite.h.in.bak src/sqlite.h.in
> 3629c3629
> < ** [sqlite3_bind_parameter_index()].
> ---
>> ** [sqlite3_bind_parameter_name()].
Actually the linktext is wrong too. So, to summarise ...
In the 'See
Le Sat, 19 Sep 2015 15:21:44 +0200,
Kees Nuyt a ?crit :
> On Sat, 19 Sep 2015 11:29:37 +0200, gwenn
> wrote:
>
> >Hello,
> >Is there any way to know when a prepared statement is recompiled ?
> >For example:
> >
> >rc = sqlite3_prepare_v2(db, "SELECT * FROM test", -1, , NULL);
> >...
> >cc =
I was thinking of dynamically building up the strings using the `nextchar`
extension but your example works just fine.
On Fri, Sep 18, 2015 at 9:52 AM, Igor Tandetnik wrote:
> On 9/18/2015 9:05 AM, Charles Leifer wrote:
>
>> As a challenge I was curious how one would write a recursive CTE to
12 matches
Mail list logo
