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
The localization problem is a complex problem. Indeed, any big database
system _should_ implement it. And yes, it can be implemented in sqlite,
and it can be activated through a PRAGMA directive. But implementing it
into sqlite (localization is not limited to numbers) would increase the
size
Bert Verhees <[EMAIL PROTECTED]> wrote:
> It is only the English speaking part of the world using Arabic numerals
> is a '.', which is a minority
> The rest uses a ','
>
SQLite uses "." as the radix point always. This is by design.
It used to use the locale specific radix point, but that led
Will Leshner wrote:
On Jan 31, 2006, at 1:42 PM, Bert Verhees wrote:
It is only the English speaking part of the world using Arabic
numerals is a '.',
And the Japanese speaking world :)
Yuo are right, and the South American speaking Spanish also
But the South American speaking
On Jan 31, 2006, at 1:42 PM, Bert Verhees wrote:
It is only the English speaking part of the world using Arabic
numerals is a '.',
And the Japanese speaking world :)
--
REALbasic news and tips: http://rbgazette.com
KidzMail & KidzBlog: http://haranbanjo.com
Bert Verhees wrote:
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
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
> > 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
Quoting Bogus?aw Brandys ([EMAIL PROTECTED]):
> 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
Let's see - you insert 12,0 in the column "price", and you're
Bogusław Brandys wrote:
Bogusław Brandys wrote:
Hello,
Maybe someone could explain me how to properly store float/decimal
values into sqlite 3.X database ?
I created test table:
create table test(number double);
insert into test(number) values(11);
Now it looks like:
11.0
so, '.'
- Original Message -
From: "Bogusław_Brandys" <[EMAIL PROTECTED]>
Hello,
Maybe someone could explain me how to properly store float/decimal values
into sqlite 3.X database ?
I created test table:
create table test(number double);
insert into test(number) values(11);
Now it looks
Bogusław Brandys wrote:
Hello,
Maybe someone could explain me how to properly store float/decimal
values into sqlite 3.X database ?
I created test table:
create table test(number double);
insert into test(number) values(11);
Now it looks like:
11.0
so, '.' seems to be always decimal
Hello,
Maybe someone could explain me how to properly store float/decimal
values into sqlite 3.X database ?
I created test table:
create table test(number double);
insert into test(number) values(11);
Now it looks like:
11.0
so, '.' seems to be always decimal separator.
But under my
13 matches
Mail list logo
