While on errata for the shell, there is a little cosmetic bugaboo with the output of .eqp full:
(1) When .mode col is in effect the "explain" column widths are used, not the .width or the defaults used when .eqp full is not in effect. (2) .head on is ignored -- table output column headers are not output. Also, if you give .eqp or .explain a nonsense argument they report that the argument must be a boolean. .explain also appears to take auto and .eqp also takes more than just a boolean (eg full). -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> On >Behalf Of Richard Hipp >Sent: Saturday, 26 October, 2019 10:08 >To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> >Subject: Re: [sqlite] Bug: Infite loop on SELECT with .explain on > >Thanks for the report. This problem is fixed on trunk. > >To be clear, this is an issue in the "sqlite3" shell command, not in >the SQLite core. > >Also, it is an issue in the deprecated and undocumented ".explain on" >command of the shell. Years ago, it used to be necessary to run >".explain on" prior to running an EXPLAIN query in order to set up the >output formatting correctly so that the EXPLAIN output was readable. >But that setup is now done automatically. There is no need to run >".explain on" any more and that dot-command is now deprecated and >undocumented. It exists only to prevent legacy scripts from blowing >up. Perhaps I should make the ".explain" command into a no-op? >-- >D. Richard Hipp >d...@sqlite.org >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
