Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-25 Thread Simon Slavin
On 25 Jul 2016, at 3:33pm, Wade, William wrote: > If too late for this release, consider it a request for the next release: > > Provide a way (pragma, or additional syntax on the command/virtual table) to > have the command-line .import, and the new CSV virtual table, use

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-25 Thread Wade, William
If too late for this release, consider it a request for the next release: Provide a way (pragma, or additional syntax on the command/virtual table) to have the command-line .import, and the new CSV virtual table, use NUMERIC column affinity when creating a new table. I like to think that 10 is

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-24 Thread Roger Binns
On 23/07/16 08:16, Richard Hipp wrote: > Draft change log: https://www.sqlite.org/draft/releaselog/3_14_0.html Please please don't make the new trace/profile API expand the SQL by default. There are two problems with expanding by default: - The text no longer matches what the programmer had in

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-24 Thread gwenn
Hello, It seems that the problem reported here: http://www.mail-archive.com/sqlite-users%40mailinglists.sqlite.org/msg97627.html is not fixed. SQLite version 3.14.0 2016-07-23 05:22:02 sqlite> select 0x1g; 1 sqlite> Regards. On Sat, Jul 23, 2016 at 5:16 PM, Richard Hipp wrote:

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-23 Thread Jan Berkel
One thing I'd love to see addressed is an issue I reported back in May: sqlite3_auto_extension + custom FTS5 tokenizer http://thread.gmane.org/gmane.comp.db.sqlite.general/101685/focus=101697 http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/2016-May/066676.html The workaround

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-23 Thread Darren Duncan
On 2016-07-23 8:16 AM, Richard Hipp wrote: The next release of SQLite will be the "pi" release - version 3.14. It will probably occur within the next two weeks. Draft change log: https://www.sqlite.org/draft/releaselog/3_14_0.html Code snapshot:

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-23 Thread Olivier Mascia
Dears, (Writing from mobile, hope the HTML like formatting, which I can't seem to override, won't be a total mess in this post). Have not even yet got to the code to test it and review the new C API but I already have a question about: Added two new C-language interfaces:

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-23 Thread R Smith
Is it too late to add a request? There's been many questions and discussions around people not knowing which Foreign Key constraint failure caused their transaction to abort (and we have been over why that is not feasible), but perhaps the new Trace hook is a great way to add an SQLITE_TRACE

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-23 Thread Igor Korot
Mr. Hipp, On Sat, Jul 23, 2016 at 11:16 AM, Richard Hipp wrote: > The next release of SQLite will be the "pi" release - version 3.14. > It will probably occur within the next two weeks. > > Draft change log: https://www.sqlite.org/draft/releaselog/3_14_0.html > > Code snapshot:

Re: [sqlite] The upcoming "pi" release of SQLite

2016-07-23 Thread Simon Slavin
On 23 Jul 2016, at 4:16pm, Richard Hipp wrote: > Testing and (especially) documentation work is on-going. If there isn't already done, would it be possible to add an option to dbhash which produces just the hash and not the path ? That would make it easier for a shell

[sqlite] The upcoming "pi" release of SQLite

2016-07-23 Thread Richard Hipp
The next release of SQLite will be the "pi" release - version 3.14. It will probably occur within the next two weeks. Draft change log: https://www.sqlite.org/draft/releaselog/3_14_0.html Code snapshot: https://www.sqlite.org/snapshot/sqlite-snapshot-201607230522.tar.gz Testing and