On 07/18/17 16:37 , Stephan Buchert wrote:
> The command history (Ctrl-R) of the shell is still intact with the new tab
> completion, but I had experienced it often as way too short (too few
> lines). So I have searched now in the source code, the line in shell.c is
>
> if( zHistory ){
>
The command history (Ctrl-R) of the shell is still intact with the new tab
completion, but I had experienced it often as way too short (too few
lines). So I have searched now in the source code, the line in shell.c is
if( zHistory ){
shell_stifle_history(100);
...
in case so
The tab completion in the sqlite3 shell works, which is nice, but it seems
to shadow readline's normal file name completion when hitting tab at for
example
sqlite> .read "sq
which is not so nice... (i.e. no file name completion any more for .read ,
.attach and the like...)
/Stephan
_
On 7/17/17, petern wrote:
> Missing documentation or wrong extension source?
The documentation and code you are looking are from different branches.
>
> https://www.sqlite.org/src/file/ext/misc/remember.c line 51:
> -> ptr = sqlite3_value_pointer(argv[1], "carray");
>
> This signature, 'void* sq
Missing documentation or wrong extension source?
https://www.sqlite.org/src/file/ext/misc/remember.c line 51:
-> ptr = sqlite3_value_pointer(argv[1], "carray");
This signature, 'void* sqlite3_value_pointer(V,T)' , is not documented here:
https://sqlite.org/draft/c3ref/value_blob.html
Nor is the
Richard Hipp wrote:
E.Pasma wrote:
Is there any otrher choice except ./configure --disable-readline.
Other options:
(1) You can upgrade the readline library on your PPC to something more
recent that supports tab completion.
(2) You can compile the shell using linenoise instead of readline.
On 7/15/17, E.Pasma wrote:
> Hello, when building the pre-release snapshot an error occurs. It is
> likely due to my outdated Mac OS version, 10.5.8.
>
> shell.c: In function ‘readline_completion’:
> shell.c:4286: warning: return makes pointer from integer without a cast
> ...
> Undefined symbols:
Hello, when building the pre-release snapshot an error occurs. It is
likely due to my outdated Mac OS version, 10.5.8.
shell.c: In function ‘readline_completion’:
shell.c:4286: warning: return makes pointer from integer without a cast
...
Undefined symbols:
"_rl_completion_matches", reference
Regarding the new pointer value/result pseudo-null API:
void *sqlite3_value_pointer(sqlite3_value*);
void sqlite3_result_pointer(sqlite3_context*, void*);
Assuming sqlite3_value_type() returns SQLITE_NULL for these pseudo-nulls,
and thinking ahead, an additional pointer type API pair would be nat
The STMT extension has been renamed as SQLITE_STMT.
Updated code is in the prerelease snapshot on
https://sqlite.org/download.html and the draft documentation
(https://sqlite.org/draft/index.html) has been updated.
--
D. Richard Hipp
d...@sqlite.org
__
I wonder how SQLITE_PREPARE_PERSISTENT can be used in a jdbc driver. Do you
have any idea?
(seems like there is no possibility to know about it from the jdbc API)
is it better to always set this flag or to never do it?
___
sqlite-users mailing list
sqlit
> perhaps the devs can invent some other namespace
Seconded. I would like to think the devs, themselves, would like to create
some sort of namespace or isolation for the structures created by the
extensions. A little more gusto in the name, rather than STMT, would always
be appreciated. imo
On Fr
On 14 Jul 2017, at 8:50am, Clemens Ladisch wrote:
> There already is an "sqlite_" namespace, and it is reserved for internal
> objects of SQLite itself.
>
> The STMT virtual table is an extension that must be explicitly enabled.
> (The sqlite3 command-line shell does so by default, but it alre
Eric Grange wrote:
>> Could I suggest that the STMT virtual table be renamed as something like
>> sqlite_statements ?
>> Or anything else that starts with "sqlite_" ?
>
> Seconded, especially as more and more virtual tables become available (a
> good thing), there is a greater risk of name collisi
> Could I suggest that the STMT virtual table be renamed as something like
sqlite_statements ?
> Or anything else that starts with "sqlite_" ?
Seconded, especially as more and more virtual tables become available (a
good thing), there is a greater risk of name collision, so an "sqlite_"
namespace
On 07/13/2017 08:49 PM, Richard Hipp wrote:
The 3.20.0 release of SQLite is expected in about a week. Please
report any issues that you have with the beta as soon as possible.
Code is available in the "prerelease snapshot" at
https://sqlite.org/download.html
An overview of changes is at http
ect: Re: [sqlite] Version 3.20.0 coming soon...
On 7/13/17, Dominique Pellé wrote:
>
> Looking at the description of the new SQLITE_PREPARE_PERSISTENT at
> https://sqlite.org/draft/c3ref/c_prepare_persistent.html
> it's not clear to me what are the benefits.
On 7/13/17, Simon Slavin wrote:
>
> Can I conclude that if "SELECT sql FROM STMT" returns no rows then closing
> the connection should work properly and immediately ?
>
You'll probably always get one row of result, which is the query itself.
Yes, if you only get that one row, then it is certainl
On 13 Jul 2017, at 7:49pm, Richard Hipp wrote:
> An overview of changes is at https://sqlite.org/draft/releaselog/3_20_0.html
Could I suggest that the STMT virtual table be renamed as something like
sqlite_statements ? Or anything else that starts with "sqlite_" ? I’m
uncomfortable with a
2 PM
To: SQLite mailing list
Subject: Re: [sqlite] Version 3.20.0 coming soon...
On 7/13/17, Dominique Pellé wrote:
>
> Looking at the description of the new SQLITE_PREPARE_PERSISTENT at
> https://sqlite.org/draft/c3ref/c_prepare_persistent.html
> it's not clear to me what a
On 7/13/17, Dominique Pellé wrote:
>
> Looking at the description of the new SQLITE_PREPARE_PERSISTENT
> at https://sqlite.org/draft/c3ref/c_prepare_persistent.html
> it's not clear to me what are the benefits.
> Shouldn't the description say why it can be beneficial to
> use it or not?
>
That do
Richard Hipp wrote:
> The 3.20.0 release of SQLite is expected in about a week. Please
> report any issues that you have with the beta as soon as possible.
>
> Code is available in the "prerelease snapshot" at
> https://sqlite.org/download.html
>
> An overview of changes is at https://sqlite.org
On 7/13/17, jungle Boogie wrote:
>
> On doesn't have to be capitalized:
> SQLite Release 3.20.0 On 2017-07-20
>
That is the same capitalization used for all prior releases (ex:
https://www.sqlite.org/releaselog/3_19_3.html and
https://www.sqlite.org/releaselog/3_0_0.html) so I think I will leave
On 13 July 2017 at 11:49, Richard Hipp wrote:
> The 3.20.0 release of SQLite is expected in about a week. Please
> report any issues that you have with the beta as soon as possible.
>
> Code is available in the "prerelease snapshot" at
> https://sqlite.org/download.html
>
> An overview of changes
On 13 July 2017 at 11:49, Richard Hipp wrote:
> The 3.20.0 release of SQLite is expected in about a week. Please
> report any issues that you have with the beta as soon as possible.
>
> Code is available in the "prerelease snapshot" at
> https://sqlite.org/download.html
>
> An overview of changes
On 7/13/17, David Raymond wrote:
> Is there a page for the LSM1 extension?
>
We were just discussing that internally. The current decision is to
omit the LSM1 bullet from the change log for this release. We need to
spend more time on that extension before it is officially announced.
The code is
To enable the STMT extension"
"in default builts of" -> "in default builds of"
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of Richard Hipp
Sent: Thursday, July 13, 2017 2:50 PM
To: General Discussion of SQLite
The 3.20.0 release of SQLite is expected in about a week. Please
report any issues that you have with the beta as soon as possible.
Code is available in the "prerelease snapshot" at
https://sqlite.org/download.html
An overview of changes is at https://sqlite.org/draft/releaselog/3_20_0.html
You
28 matches
Mail list logo