| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Bo?ena Potempa <Bozena(dot)Potempa(at)otc(dot)pl> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL+ Beta bug? |
| Date: | 2002-11-21 00:36:33 |
| Message-ID: | 3DDC2A91.3F4FCDE4@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Bo?ena Potempa wrote:
>
> [..]
> >According to an ODBC related document, the behavior of ODBC
> >functions in such case is undefined and it is driver-specific
> >if a driver handles this correctly.
>
> OK. If it is driver-specific then why don't allow users to
> to use this feature if it is implemented in the server?
If it is implemented in the server I would implement it.
However, it isn't implemented in the server and so
there's no recommended way to store 0s in strings now.
Even if 0s are stored in strings accidentally like your
example shows, there are few code which take them into
account and they would be lost before long. As for me
I've never minded 0s in strings in the backend coding.
I don't think your request is unreasonable but what
you should request the change first seems from the
backend side.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Han | 2002-11-21 06:52:37 | Problems about ODBC3 datetime |
| Previous Message | Joan Picanyol i Puig | 2002-11-21 00:00:22 | Re: insert into view with a defined rule fails from MSAccess |