[sqlalchemy] Re: Numeric not consistent between Postgres and Oracle in 0.6

So what is the correct way to get specify a double precision number with postgres? Thanks - Rich On May 6, 9:36 am, Michael Bayer mike...@zzzcomputing.com wrote: On May 6, 2010, at 12:23 PM, Kent wrote: I guess my suggestion is:  since Oracle takes DECIMAL andNUMERICto mean NUMBER(38), if

Re: [sqlalchemy] Re: Numeric not consistent between Postgres and Oracle in 0.6

Numeric(precision, scale) On May 25, 2010, at 4:07 PM, Rich wrote: So what is the correct way to get specify a double precision number with postgres? Thanks - Rich On May 6, 9:36 am, Michael Bayer mike...@zzzcomputing.com wrote: On May 6, 2010, at 12:23 PM, Kent wrote: I guess my

[sqlalchemy] Re: Numeric not consistent between Postgres and Oracle in 0.6

I guess my suggestion is: since Oracle takes DECIMAL and NUMERIC to mean NUMBER(38), if SQLAlchemy interprets the generic types DECIMAL or Numeric with no precision to allow for decimal or integer values, we should translate that to 'NUMBER' for Oracle... Thoughts? On May 6, 12:11 pm, Kent

Re: [sqlalchemy] Re: Numeric not consistent between Postgres and Oracle in 0.6

On May 6, 2010, at 12:23 PM, Kent wrote: I guess my suggestion is: since Oracle takes DECIMAL and NUMERIC to mean NUMBER(38), if SQLAlchemy interprets the generic types DECIMAL or Numeric with no precision to allow for decimal or integer values, we should translate that to 'NUMBER' for