- Original Message -
From: Chris Johnson [EMAIL PROTECTED]
To: Jim Dickenson [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, September 18, 2001 8:01 AM
Subject: Re: NUMERIC field contents
On Sun, Sep 16, 2001 at 02:11:20PM -0700, Jim Dickenson wrote:
Does anyone have an opinion about
The problem is that a number that is in the
MySQL database might be a magnitude of 10 times larger than a number that
is
in the PostgreSQL database.
Could you explain this?
dpk
-
Before posting, please check:
On 9/18/01 11:25 AM, Dana Powers at [EMAIL PROTECTED] wrote:
The problem is that a number that is in the
MySQL database might be a magnitude of 10 times larger than a number that
is
in the PostgreSQL database.
Could you explain this?
dpk
PM
Subject: Re: NUMERIC field contents
On 9/18/01 11:25 AM, Dana Powers at [EMAIL PROTECTED] wrote:
The problem is that a number that is in the
MySQL database might be a magnitude of 10 times larger than a number
that
is
in the PostgreSQL database.
Could you explain this?
dpk
PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, September 18, 2001 1:35 PM
Subject: Re: NUMERIC field contents
On 9/18/01 11:25 AM, Dana Powers at [EMAIL PROTECTED] wrote:
The problem is that a number that is in the
MySQL database might be a magnitude of 10 times larger than a number
On Tue, Sep 18, 2001 at 01:45:30PM -0700, Dana Powers wrote:
And my question is, if you've defined your column to have (10,2) precision,
why would you try to insert a higher precision number?
Perhaps he's writing a report, and the application needs to know the
size of the data to expect. It's
