Hello Richard !
Today the server https://www3.sqlite.org/ is not working, I usually
follow the sqlite3 repository daily and I think that could be a good
idea to add an option to fossil update command to allow override the url
for the repository so in cases like today I could do:
fossil
On 9/11/18, heribert wrote:
> I've a prepared select statement (the database is in :memory: based.).
> After binding the input values, calling next, checking the result type
> of a text column, sometimes the follwing sqlite3_column_text returns
> with a nullptr.
>
> The stange thing is: the prior
I've a prepared select statement (the database is in :memory: based.).
After binding the input values, calling next, checking the result type
of a text column, sometimes the follwing sqlite3_column_text returns
with a nullptr.
The stange thing is: the prior called sqlite3_column_type do not
You are assuming that the column is either NULL or a SQLITE_TEXT value. This
assumption is obviously violated by the real data returned by your query (which
you do not show).
A second possibility would be that another thread has done something to your
prepared statement between retrieving the
Thx Gunter...
that's the problem. I've capsuled the sqlite access in some database
classes. So i have only the call a function named getProperty with some
parameters.
But in some cases it may be possible that the instance of the object
calls this function from another thread (with the same
Thanks for your answer Eric,Sandu
About the first idea of Eric I have to say its correct for me when I do a
test with another fts5 table with no huge rows but my database has that
problem.And about the other possibility I tested that before to set "*"at
the first and end of the match but I have
It seems like there is an opportunity for improvement on updates if an index
contains expressions.
In the following example:
CREATE TABLE Foo(x, y, z);
CREATE INDEX FooX on Foo(x);
CREATE INDEX FooZ on Foo(z);
CREATE INDEX FooLenZ on Foo(length(z));
explain UPDATE foo SET x=1 WHERE rowid=1;
I
On 09/11/2018 01:26 PM, Maziar Parsijani wrote:
Thanks for your answer Eric,Sandu
About the first idea of Eric I have to say its correct for me when I do a
test with another fts5 table with no huge rows but my database has that
problem.And about the other possibility I tested that before to set
On Sep 11, 2018, at 2:29 AM, Domingo Alvarez Duarte wrote:
>
> I think that could be a good idea to add an option to fossil update command
> to allow override the url for the repository so in cases like today I could
> do:
>
> fossil updata --url https://www1.sqlite.org/cgi/src
There are
We are in final testing for SQLite 3.25.0. Details on this release
can be seen at
https://www.sqlite.org/draft/releaselog/3_25_0.html
There will be no further enhancements before the release. Bug fixes
only. You can follow the progress of testing at
> On Sep 11, 2018, at 8:07 PM, Richard Hipp wrote:
>
> We are in final testing for SQLite 3.25.0. Details on this release
> can be seen at
>
> https://www.sqlite.org/draft/releaselog/3_25_0.html
Window Functions! Hurray! Hurray! :)
https://www.sqlite.org/draft/windowfunctions.html
Wow, ALTER TABLE RENAME COLUMN is going to help KEXI, thanks for that!
On Tue, 11 Sep 2018 at 20:07, Richard Hipp wrote:
> We are in final testing for SQLite 3.25.0. Details on this release
> can be seen at
>
> https://www.sqlite.org/draft/releaselog/3_25_0.html
>
> There will be no
On Tue, 11 Sep 2018 at 11:08, Richard Hipp wrote:
>
> We are in final testing for SQLite 3.25.0. Details on this release
> can be seen at
>
> https://www.sqlite.org/draft/releaselog/3_25_0.html
>
> There will be no further enhancements before the release. Bug fixes
> only. You can follow
13 matches
Mail list logo
