| From: | <noreply(at)pgfoundry(dot)org> |
|---|---|
| To: | noreply(at)pgfoundry(dot)org |
| Subject: | [ psqlodbc-Bugs-1010864 ] CODBCFieldInfo field type (m_nSQLType) is incorrect |
| Date: | 2010-08-05 21:39:14 |
| Message-ID: | 20100805213914.3481810716D0@pgfoundry.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Bugs item #1010864, was opened at 2010-08-05 14:39
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010864&group_id=1000125
Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Mark Richardson (markmapo)
Assigned to: Nobody (None)
Summary: CODBCFieldInfo field type (m_nSQLType) is incorrect
Initial Comment:
Using the CRecordset.GetODBCFieldInfo() function to retrieve a CODBCFieldInfo about the field give incorrect values for the types. I only checked a couple types agains an access database...
db_table_type postgres_value access_value
int 4 5
double 6 8
What are the values supposed to be? Far as I can tell they are the values which come from "atldbcli.h" & "oledb.h" - but these don't match with the access values either (poor documentation on what these values are supposed to be from MS about ODBC - suprise?no)
Also, the CRecordSet.GetTableName() is unset (so is the access database value). I don't like the way that a table name is assigned to an entire CRecordset, as each field MAY be from a different table. I prefer the way postgres has a table name for each field - but we're stuck using the ODBC interface.
Thanks guys for all the great work!
Mark
----------------------------------------------------------------------
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010864&group_id=1000125
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Calvin | 2010-08-09 17:13:46 | Moving data from SQL Server to Postgres via VFP ODBC Driver |
| Previous Message | noreply | 2010-08-05 18:43:02 | [ psqlodbc-Bugs-1010862 ] Will not run on Windows 2000 and older, missing symbols |