From: | Peter Koczan <pjkoczan(at)gmail(dot)com> |
---|---|
To: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Domains, casts, and MS Access |
Date: | 2010-08-04 18:51:00 |
Message-ID: | AANLkTimP3GxKof7_r7VrpjWJRM1HjUC11RnHKyyiyS4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Wed, Aug 4, 2010 at 12:47 PM, Richard Broersma
<richard(dot)broersma(at)gmail(dot)com> wrote:
> 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?
This is one of my first forays into ODBC, so I didn't know that was a
possibility. Is there any place where these are documented? Searching
for ODBC options yields info on connection options, but none on
behavior that I could find.
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma | 2010-08-04 18:56:21 | Re: Domains, casts, and MS Access |
Previous Message | Steve Wampler | 2010-08-04 17:50:51 | Re: What does PostgreSQL do when time goes backward? |