Hi,
working with sqlite and mysql, noticed that they're different in regard of
mixed types.
Select '24' 25
Select 24 25
have the same results in MySql and different sqlite.
Actually it's no news (my sqlite queries contained CAST(.. as INT) ), but I
decided to look at the docs and noticed
On Fri, Feb 10, 2012 at 6:11 AM, Max Vlasov max.vla...@gmail.com wrote:
Hi,
working with sqlite and mysql, noticed that they're different in regard of
mixed types.
Select '24' 25
Select 24 25
have the same results in MySql and different sqlite.
Actually it's no news (my sqlite queries
On Fri, Feb 10, 2012 at 4:53 PM, Richard Hipp d...@sqlite.org wrote:
On Fri, Feb 10, 2012 at 6:11 AM, Max Vlasov max.vla...@gmail.com wrote:
Hi,
working with sqlite and mysql, noticed that they're different in regard
of
mixed types.
Select '24' 25
Select 24 25
have the same
Max Vlasov max.vla...@gmail.com wrote:
On Fri, Feb 10, 2012 at 4:53 PM, Richard Hipp d...@sqlite.org wrote:
In the statement:
SELECT '25' 25;
There are no columns, only literals. And hence no affinity is applied.
So if a string looks like a numeral it should be treated as numeral
On Fri, Feb 10, 2012 at 5:45 PM, Igor Tandetnik itandet...@mvps.org wrote:
Value has TEXT affinity, 5 has none. So 5 is converted to '5', and then
lexicographic comparisons are performed. It so happens that all strings in
the Value column lexicographically precede '5'.
If you wanted Value to
