| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ludek Finstrle <luf(at)pzkagis(dot)cz> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4 |
| Date: | 2005-12-06 19:07:13 |
| Message-ID: | 15186.1133896033@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces pgsql-odbc |
Ludek Finstrle <luf(at)pzkagis(dot)cz> writes:
> I don't want to reinvent the wheel.
Why do you feel a need to distinguish the domain from its underlying
type on the client side? They're the same as regards representation
and so on.
The reason for the backend change was that client-side drivers (such as
JDBC and ODBC) want to know the underlying datatype so that they know
what representation to use etc. Distinguishing domains made their job
harder not easier.
If you want an add-on datatype that is really different from OID, then
make a real datatype (CREATE TYPE). You can still piggyback on OID as
the representation type --- steal its I/O functions and so on.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ludek Finstrle | 2005-12-06 19:27:49 | Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4 |
| Previous Message | Ludek Finstrle | 2005-12-06 18:44:02 | Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ludek Finstrle | 2005-12-06 19:27:49 | Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4 |
| Previous Message | Ludek Finstrle | 2005-12-06 18:44:02 | Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4 |