Re: [sqlite] dynamic typing misunderstanding

Hello! On Monday 01 March 2010 14:48:46 Dan Kennedy wrote: > > On Mar 1, 2010, at 6:08 PM, Alexey Pechnikov wrote: > > >> It would seem to me that asking [1='1'] *should* return false > >> because the > >> numeric and character string value domains are logically disjoint, > >> so no value >

Re: [sqlite] dynamic typing misunderstanding

On Mar 1, 2010, at 6:08 PM, Alexey Pechnikov wrote: >> It would seem to me that asking [1='1'] *should* return false >> because the >> numeric and character string value domains are logically disjoint, >> so no value >> from one could ever equal a value from another, and so SQLite's >>

Re: [sqlite] dynamic typing misunderstanding

Hello! On Monday 01 March 2010 08:05:06 Darren Duncan wrote: > Alexey Pechnikov wrote: > > Hello! > > > > On Thursday 25 February 2010 02:53:32 Igor Tandetnik wrote: > >> http://www.sqlite.org/datatype3.html > >> For conversions between TEXT and REAL storage classes, SQLite considers > >> the

Re: [sqlite] dynamic typing misunderstanding

Alexey Pechnikov wrote: > Hello! > > On Thursday 25 February 2010 02:53:32 Igor Tandetnik wrote: >> http://www.sqlite.org/datatype3.html >> For conversions between TEXT and REAL storage classes, SQLite considers the >> conversion to be lossless and reversible if the first 15 significant decimal

Re: [sqlite] dynamic typing misunderstanding

Hello! On Thursday 25 February 2010 02:53:32 Igor Tandetnik wrote: > http://www.sqlite.org/datatype3.html > For conversions between TEXT and REAL storage classes, SQLite considers the > conversion to be lossless and reversible if the first 15 significant decimal > digits of the number are

Re: [sqlite] dynamic typing misunderstanding

On Wed, Feb 24, 2010 at 5:54 PM, eternelmangekyosharingan wrote: > I'm sorry but I don't get your answer. > Can you provide further explanations, please ? Well, it is entirely possible that I have not understood your question, and from Igor and Dan's answers,

Re: [sqlite] dynamic typing misunderstanding

Igor Tandetnik wrote: > eternelmangekyosharingan > > wrote: > >> I create the following table: >> sqlite> create table t1(a); >> sqlite> insert into t1 values(123456789.123456789); >> >> I ran the following commands: >> sqlite> select * from t1; >>

Re: [sqlite] dynamic typing misunderstanding

Igor, thanks for your reply. I read that too. But it does not make any sense to me as any number will be truncated according to this definition. Can you give me an example where an REAL is converted to a TEXT due to a conversion loss ? On Thu, Feb 25, 2010 at 12:54 AM,

Re: [sqlite] dynamic typing misunderstanding

I'm sorry but I don't get your answer. Can you provide further explanations, please ? On Thu, Feb 25, 2010 at 12:40 AM, P Kishor wrote: > On Wed, Feb 24, 2010 at 5:22 PM, eternelmangekyosharingan > wrote: > > Hello all, > > > > I create

Re: [sqlite] dynamic typing misunderstanding

eternelmangekyosharingan wrote: > I create the following table: > sqlite> create table t1(a); > sqlite> insert into t1 values(123456789.123456789); > > I ran the following commands: > sqlite> select * from t1; > 123456789.123457 > sqlite> select typeof(a)

Re: [sqlite] dynamic typing misunderstanding

On Wed, Feb 24, 2010 at 5:22 PM, eternelmangekyosharingan wrote: > Hello all, > > I create the following table: > sqlite> create table t1(a); > sqlite> insert into t1 values(123456789.123456789); > > I ran the following commands: > sqlite> select * from t1; >

[sqlite] dynamic typing misunderstanding

Hello all, I create the following table: sqlite> create table t1(a); sqlite> insert into t1 values(123456789.123456789); I ran the following commands: sqlite> select * from t1; 123456789.123457 sqlite> select typeof(a) from t1; real What I expected to get is: sqlite> select * from t1;