| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: using domain types with ODBC, esp. lo |
| Date: | 2003-03-21 16:31:52 |
| Message-ID: | 13532.1048264312@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces pgsql-odbc |
Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de> writes:
> The well-known data types PG_TYPE_DATETIME, PG_TYPE_TIMESTAMP_NO_TMZONE,
> PG_TYPE_TIME, PT_TYPE_TIME_WITH_TMZONE are handled in a special way
> concerning the atttypmod field. This will fail for domain types of that
> base type.
This is correct, since the domain won't expose the atttypmod it assigns
to the underlying type.
> Actually, best thing for this problems would be if the backend would
> deliver the base type oid, not the user type oid.
There was some discussion of that idea in pgsql-hackers last week, but
we didn't come to a definite conclusion. How do others feel about it?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2003-03-21 16:48:20 | Re: using domain types with ODBC, esp. lo |
| Previous Message | Andreas Pflug | 2003-03-21 16:19:51 | using domain types with ODBC, esp. lo |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2003-03-21 16:36:10 | ODBC driver settings for BLOBs |
| Previous Message | Andreas Pflug | 2003-03-21 16:19:51 | using domain types with ODBC, esp. lo |