Thread: Issue with editing float8 fields
I'm guessing float8 is deprecated since I don't see it in the list of options when creating fields. I have an older table that has a field of type float8. I'm using PgAdmin III 1.6 Beta 1, Sep 12 2006, rev: 5353 on a windows 2000 machine. When I try to edit data in this table -> editing the float8 field, it gives me an error 'syntax error at or near "precision" at character 51' As far as I can tell, there is nothing I can put in that field that would work. If I try to edit from Microsoft Access using the ODBC driver as a linked table, I can edit the field fine. As a general note I see that according to the table header, the field is being treated as a double precision for editing purposes. ----------------------------------------- The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Obe, Regina > Sent: 29 September 2006 13:49 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] Issue with editing float8 fields > > I'm guessing float8 is deprecated since I don't see it in the list of > > options when creating fields. I have an older table that has > a field of > > type float8. No, pgAdmin just uses the SQL spec name now which is "double precision". See http://www.postgresql.org/docs/8.1/interactive/datatype.html#DATATYPE-TA BLE for a more complete list. > > I'm using PgAdmin III 1.6 Beta 1, Sep 12 2006, rev: 5353 on a windows > > 2000 machine. > > When I try to edit data in this table -> editing the float8 field, it > > gives me an error > > > 'syntax error at or near "precision" at character 51' > Please try the newer snapshot at: http://developer.pgadmin.org/snapshots/win32/pgadmin3-20060921-Win32.zip . The bug you see has been fixed. Regards, Dave.