Re: [sqlite] [sqlite-dev] SQLite version 3.7.16

On Tue, Mar 19, 2013 at 6:18 PM, Petite Abeille wrote: > > On Mar 19, 2013, at 1:33 PM, D. Richard Hipp wrote: > > > http://www.sqlite.org/releaselog/3_7_16.html > > • Enhance the spellfix1 extension so that the edit distance cost table can > be

Re: [sqlite] [sqlite-dev] SQLite version 3.7.16

On Mar 19, 2013, at 1:33 PM, D. Richard Hipp wrote: > http://www.sqlite.org/releaselog/3_7_16.html • Enhance the spellfix1 extension so that the edit distance cost table can be changed at runtime by inserting a string like 'edit_cost_table=TABLE' into the "command" field.

Re: [sqlite] SQLite version 3.7.16

On Tue, Mar 19, 2013 at 3:43 PM, Levi Haskell (BLOOMBERG/ 731 LEXIN) < lhask...@bloomberg.net> wrote: > Hi Richard, > > Downloaded the 3.7.16. I still don't see any mentioning of the optional > table argument to the foreign_key_check pragma in: >

Re: [sqlite] SQLite version 3.7.16

Hi Richard, Downloaded the 3.7.16. I still don't see any mentioning of the optional table argument to the foreign_key_check pragma in: http://www.sqlite.org/pragma.html#pragma_foreign_key_check Is this feature officially unsupported? Thanks, - Levi

[sqlite] SQLite version 3.7.16

SQLite version 3.7.16 is now available on the SQLite website http://www.sqlite.org/ SQLite version 3.7.16 is a regularly scheduled release of SQLite. This release contains several langauge enhancements and improvements to the query optimizer. A list of the major enhancements and

Re: [sqlite] Inserting a CURRENT_TIMESTAMP value into a BIG INT column seems to work

On 3/19/2013 7:51 AM, Philipp Kursawe wrote: This goes through without an error and the physical db file then really contains the current timestamp as a string. How can that be? Is the column internally converted on the fly? http://sqlite.org/datatype3.html -- Igor Tandetnik

Re: [sqlite] Inserting a CURRENT_TIMESTAMP value into a BIG INT column seems to work

On 19 Mar 2013, at 11:51am, Philipp Kursawe wrote: > CREATE TABLE test (dt BIG INT) Note that SQLite does not have a BIG INT type. The text you show there will result in a column with INTEGER affinity. > and inserted a value: > INSERT INTO test

Re: [sqlite] Inserting a CURRENT_TIMESTAMP value into a BIG INT column seems to work

On Tue, Mar 19, 2013 at 12:51 PM, Philipp Kursawe wrote: > I created this table > CREATE TABLE test (dt BIG INT) > and inserted a value: > INSERT INTO test VALUES(CURRENT_TIMESTAMP) > > This goes through without an error and the physical db file then really > contains the

[sqlite] Inserting a CURRENT_TIMESTAMP value into a BIG INT column seems to work

I created this table CREATE TABLE test (dt BIG INT) and inserted a value: INSERT INTO test VALUES(CURRENT_TIMESTAMP) This goes through without an error and the physical db file then really contains the current timestamp as a string. How can that be? Is the column internally converted on the fly?