Carl Jacobs wrote:
>
> > > All would be fine but look at this :
> > >
> > > create table test(
> > > price double,
> > > amount double default 0
> > > );
> > >
> > > insert into test(price) values("12,0");
> > >
> > > amount now = 0.0
>
> The world seems to have settled on using Arabic numerals 0, 1, 2 ... 9. I
> think we should think about settling on . as the decimal separator, it would
> save a bit of confusion if we all used the same notation.
>
> I suspect that "12,0" is being stored as a string. Don't forget that for all
> intents and purposes sqlite3 is typless, so it will store your value in
> whatever is the most compact form. So, if you want to, you can store a
> picture of yourself in field price!
>
> Regards,
> Carl.
Older English books on mathematical and physical subjects use a dot that
is
centred on the line, not the period we are now accustomed to, because
that
particular glyph is simply not present on the keyboard. I can think of a
lot
of other typograhical conventions that have lost the battle against the
relentless keyboard. Oh well, I suppose I am getting old ;).
As for the design decision that Richard mentions in his reply, I quite
agree: it is better to stick to that one radix point than to try and
satisfy all people - I have seen a lot of sorrow and hardship from the
imperfect attempts to do otherwise. (I will just bring in the example
of older versions of MS Excel where a dot or a comma in a file would
make it unusable on a machine with a different regional setting).
A helper function to sort this out would be the solution to go for.
Regards,
Arjen
