Re: [sqlite] Is VACUUM ANALYZE removed?

2018-05-19 22:21 GMT+09:00 Richard Hipp : > On 5/19/18, Kenichi Ishigaki wrote: >> Hi. >> >> VACUUM ANALYZE without a semicolon in-between used to work, but it >> seems not since 3.15.0. I couldn't find an entry for this in >> releaselogs. Is it an intentio

[sqlite] Is VACUUM ANALYZE removed?

Hi. VACUUM ANALYZE without a semicolon in-between used to work, but it seems not since 3.15.0. I couldn't find an entry for this in releaselogs. Is it an intentional change, or a regression? Regards, Kenichi ___ sqlite-users mailing list sqlite-users@ma

Re: [sqlite] regression since 3.20.0

2018-01-27 22:59 GMT+09:00 Richard Hipp : > On 1/26/18, Kenichi Ishigaki wrote: >> Hi, >> >> I've got a regression report from a DBIx::Class perl module maintainer >> that recent SQLite (3.20.0 and onward) returns a different result from >> the previous v

[sqlite] regression since 3.20.0

onward) 1, 4, 5 If cd_idx_genreid index is not created, SQLite 3.20.0 and onward also return the expected one. Best regards, Kenichi Ishigaki ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/ma

Re: [sqlite] SQLite 3.12 refuses to load fts3 tokenizer in Tcl and Perl DBD::SQLite (or missing api for scripting case)

bindings like DBD::SQLite. > # This is why I propose (2) too here. > As for the latest developer release of DBD::SQLite for perl (since version 1.51_01 to be exact), you can set SQLITE_ENABLE_FTS3_TOKENIZER environmental variable to true to enable fts3 tokenizer when you run its Makefile.P

Re: [sqlite] segmentation fault with 3.8.0

Thank you for the fix! Kenichi Ishigaki 2013/8/30 Marc L. Allen : > Thanks... that certainly clarifies it. Also, thanks to Dan who responded > similarly. > > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Beha

[sqlite] segmentation fault with 3.8.0

Hi. I've just got a segmentation fault report with SQLite 3.8.0 from one of the perl binding users. The following set of SQL statements should reporduce the issue. Regards, Kenichi Ishigaki CREATE TABLE "twokeys" ( "artist" integer NOT NULL, "cd" integer N

Re: [sqlite] possible ordering issue since 3.7.15

Thank you for clarification. I'll forward this to the original reporter and add a note about this to our library. Regards, Kenichi Ishigaki 2013/4/14 Jay A. Kreibich : > On Sat, Apr 13, 2013 at 11:25:41PM +0700, Dan Kennedy scratched on the wall: >> On 04/13/2013 11:22 PM, ke

[sqlite] possible ordering issue since 3.7.15

Hi. I received a report that the result of the following SQL has changed since 3.7.15. I haven't looked into the sqlite source yet, but can we call this a bug? Regards, Kenichi Ishigaki - create table cd (id integer primary key, title unique, year); insert into cd (title, year) v