r
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ron Johnson
> Sent: Monday, August 28, 2006 6:27 PM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Precision of data types and functions
>
> Brandon Aiken
On Fri, 2006-09-01 at 13:33, Brandon Aiken wrote:
> Of course the year exists. The date itself is nonsensical, however.
>
> 'January 3, 648' does reference a valid day, but the date itself has no
> meaning at that time in the world, so there is very little meaning in
> using Gregorian dates excep
On Fri, 2006-09-01 at 13:33, Brandon Aiken wrote:
> -Original Message-
> From: Scott Marlowe [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 01, 2006 2:27 PM
> To: Brandon Aiken
> Cc: pgsql general
> Subject: RE: [GENERAL] Precision of data types and functions
>
: [GENERAL] Precision of data types and functions
On Fri, 2006-09-01 at 13:24, Brandon Aiken wrote:
> > Now, MySQL's design to 9-fill fields when you try to enter a
too-large
> > number is, in fact, stupid on MySQL's part. I consider that silent
> > truncation. Heck, MySQL l
On Fri, 2006-09-01 at 13:24, Brandon Aiken wrote:
> > Now, MySQL's design to 9-fill fields when you try to enter a too-large
> > number is, in fact, stupid on MySQL's part. I consider that silent
> > truncation. Heck, MySQL lets you create a date on February 31st, or
> > prior to the year 1500, b
neral
Subject: Re: [GENERAL] Precision of data types and functions
On Fri, 2006-09-01 at 10:37, Brandon Aiken wrote:
> Oh, I'm not saying that MySQL is a full-featured database, nor saying
> that I agree with the MySQL philosophy. I don't. That's why I'm
trying
&
On Fri, 2006-09-01 at 10:37, Brandon Aiken wrote:
> Oh, I'm not saying that MySQL is a full-featured database, nor saying
> that I agree with the MySQL philosophy. I don't. That's why I'm trying
> to avoid MySQL.
>
> However PostgreSQL isn't any more accurate with FLOATs than MySQL is.
> The A
a date on February 31st, or
prior to the year 1500, both of which are obviously nonsensical.
--
Brandon Aiken
CS/IT Systems Engineer
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ron Johnson
Sent: Monday, August 28, 2006 6:27 PM
To: pgsql-general@postg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon Aiken wrote:
> To be fair, that's the fault of the previous designer, not MySQL.
> You don't blame Stanley when your contractor uses 2" plain nails
> when he needed 3" galvanized. The tool isn't to blame just
> because someone used it incorrec
Tom Lane <[EMAIL PROTECTED]> writes:
> Bruce and some other people thought this was confusing, so it's been
> changed for 8.2.
No kidding. They confused me.
Well Thanks for the explanation,
The new messages are infinitely clearer
--
greg
---(end of broadcast)
I wrote:
> No, I think Bruce fixed this recently. It's just a cosmetic mistake in
> the error message so we didn't back-patch it.
No, strike that, I remember the discussion now. The pre-8.2 code is
correct on its own terms, which is that it's telling you what size
number you tried to put in:
re
Gregory Stark <[EMAIL PROTECTED]> writes:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
>> test=> insert into test values (123123123123123.2);
>> ERROR: numeric field overflow
>> DETAIL: The absolute value is greater than or equal to 10^14 for field
>> with precision 12, scale 2.
> Uhm 10^14? What
er
-Original Message-
From: Jorge Godoy [mailto:[EMAIL PROTECTED]
Sent: Monday, August 28, 2006 3:36 PM
To: Brandon Aiken
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Precision of data types and functions
"Brandon Aiken" <[EMAIL PROTECTED]> writes:
> Oh, I agr
"Brandon Aiken" <[EMAIL PROTECTED]> writes:
> Oh, I agree. PostgreSQL is a much more well-behaved RDBMS than MySQL
> ever was. I'm more inclined to select PostgreSQL over MySQL, but I may
> not be able to convince management that it's a better choice no matter
> how technically superior I can sh
On Mon, 2006-08-28 at 13:54, Gregory Stark wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
>
> > test=> create table test (a numeric(12,2));
> > CREATE TABLE
> > test=> insert into test values (123123123123123.2);
> > ERROR: numeric field overflow
> > DETAIL: The absolute value is greater tha
Scott Marlowe <[EMAIL PROTECTED]> writes:
> test=> create table test (a numeric(12,2));
> CREATE TABLE
> test=> insert into test values (123123123123123.2);
> ERROR: numeric field overflow
> DETAIL: The absolute value is greater than or equal to 10^14 for field
> with precision 12, scale 2.
Uh
IT Systems Engineer
-Original Message-
From: Scott Marlowe [mailto:[EMAIL PROTECTED]
Sent: Monday, August 28, 2006 2:21 PM
To: Brandon Aiken
Cc: pgsql general
Subject: Re: [GENERAL] Precision of data types and functions
On Mon, 2006-08-28 at 12:28, Brandon Aiken wrote:
> I'm considering m
On Mon, 2006-08-28 at 12:28, Brandon Aiken wrote:
> I'm considering migrating our MySQL 4.1 database (barf!) to PostgreSQL 8
> or MySQL 5.
>
> The guy who originally designed the system made all the number data
> FLOATs, even for currency items. Unsurprisingly, we've noticed math
> errors resul
"Brandon Aiken" <[EMAIL PROTECTED]> writes:
> I'm considering migrating our MySQL 4.1 database (barf!) to PostgreSQL 8
> or MySQL 5.
>
> The guy who originally designed the system made all the number data
> FLOATs, even for currency items. Unsurprisingly, we've noticed math
> errors resulting f
19 matches
Mail list logo
