| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Peter Koczan <pjkoczan(at)gmail(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Domains, casts, and MS Access |
| Date: | 2010-08-04 17:47:04 |
| Message-ID: | AANLkTim5LFi2pGHoVOhyscWDxpvRUEZdGQ0vxMkOEppT@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Wed, Aug 4, 2010 at 10:31 AM, Peter Koczan <pjkoczan(at)gmail(dot)com> wrote:
> One of the snags that's popped up is that there's some incompatibility
> between data types. Specifically, many fields are the Sybase type
> "bit", which is basically a boolean, but it accepts and displays
> bareword 1 and 0 instead of 't' and 'f'. For the sake of compatibility
> (especially bareword integers in queries), I've defined a 'sybit' type
> in postgres to be a domain.
One thought would be see if ODBC configuration options will achieve
this for you. Have you already exhausted this option?
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Wampler | 2010-08-04 17:50:51 | Re: What does PostgreSQL do when time goes backward? |
| Previous Message | Peter Koczan | 2010-08-04 17:31:38 | Domains, casts, and MS Access |