On 6/11/17, Balaji Ramanathan wrote:
>
> Everything was working fine under 3.15. I just use the commandline
> tool (sqlite.exe) to interact with my database. I am not a programmer and
> don't have a need for programmatic access to this database. I recently
>
Sorry,
I didn't know that VACUUM uses ATTACH.
On Sun, Jun 11, 2017 at 1:03 PM, Richard Hipp wrote:
> Have you tried this? I don't think it will work. IIRC, VACUUM uses
> ATTACH internally.
>
> On 6/11/17, gwenn wrote:
>> Hello,
>>
>> %ifndef
Thank you very much, Dr. Hipp. I am glad I was not imagining a problem
that nobody else could reproduce. If you need any additional details or if
you can think of any other way I can help with the investigation, please
let me know.
Balaji Ramanathan
PS: This is going to sound stupid, but I
On 11 Jun 2017, at 2:56pm, Balaji Ramanathan
wrote:
> This is going to sound stupid, but I would like to know how to
> download older versions of sqlite.
Although the download page gives links only for the current version of SQLite,
several older versions are
On 9 June 2017 at 22:30, Yuriy M. Kaminskiy wrote:
>
> Don't know about windows, but on linux no additional "debug privileges"
> needed. You can attach debugger (ptrace syscall) to any process running
> with under same user. Additional privileges needed only for debugging
>
Hello,
%ifndef SQLITE_OMIT_VACUUM
%ifndef SQLITE_OMIT_ATTACH
cmd ::= VACUUM.{sqlite3Vacuum(pParse,0);}
cmd ::= VACUUM nm(X). {sqlite3Vacuum(pParse,);}
%endif SQLITE_OMIT_ATTACH
%endif SQLITE_OMIT_VACUUM
should be
%ifndef SQLITE_OMIT_VACUUM
cmd ::= VACUUM.
explain query plan select * from TripDetails
Causes problems as well.
RBS
On Sun, Jun 11, 2017 at 5:27 AM, Balaji Ramanathan <
balaji.ramanat...@gmail.com> wrote:
> Hi,
>
> I maintain a personal database on sqlite. It is quite small, with
> about 30 tables, and an equal number of views.
(To clarify, the '$.hash' as the second parameter of json_extract is
specifying to extract the 'hash' attribute from the root of the JSON object
stored in the json column, per
https://sqlite.org/json1.html#compiling_the_json1_extension )
On Fri, Jun 9, 2017 at 9:04 PM, Zach C.
I did try the colon-style formatting as well, it didn't work. I didn't know
about [string map], but I tried it too, no luck:
% set map [dict create <> NotImportant]
<> NotImportant
% mydb eval [string map $map {SELECT json FROM <> WHERE
json_extract(json, '$.hash') = $hash}]
%
On Fri, Jun 9,
% mydb eval "SELECT json FROM $table WHERE json_extract(json, '\$.hash') =
\$hash"
% mydb eval "SELECT json FROM $table WHERE json_extract(json, '$.hash') =
$hash"
{{"a": "b", "hash": 244718899}}
I know, I _really_ don't want Tcl interpolating $hash directly in here, but
sqlite3's Tcl package
I was partially unclear with using a constant table name here; what I
actually need as well is the table name as effectively a const that I
control as well. So more like
mydb eval {$SELECT json FROM $table WHERE json_extract(json, '$.hash') =
$someId}
The problem is this will cause $table to be
Have you tried this? I don't think it will work. IIRC, VACUUM uses
ATTACH internally.
On 6/11/17, gwenn wrote:
> Hello,
>
> %ifndef SQLITE_OMIT_VACUUM
> %ifndef SQLITE_OMIT_ATTACH
> cmd ::= VACUUM.{sqlite3Vacuum(pParse,0);}
> cmd ::= VACUUM nm(X).
12 matches
Mail list logo