DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=UiHOS9eSlUE1M1yunOGe+Z4pbVugdCnPYgGpccI58jg2fyv/pV6184x/qEiGT5RV6G
	J6iXsJ/8X6WpMBSRRFI558xskDaAn7RCkf1soh0iol26Ln8VroKFkOcfVQYlo9Qg10NP
	Pa0Mw6v4jzI8+Amu5BLgAIzotF1xZ1tl1xZ6U=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=3HQborwBRTMfiPtKDFzRzQLtkHJ-E=m31vkUT@mail.gmail.com>
References: <AANLkTi=3HQborwBRTMfiPtKDFzRzQLtkHJ-E=m31vkUT@mail.gmail.com>
Date: Wed, 4 Aug 2010 10:47:04 -0700
Message-ID: <AANLkTim5LFi2pGHoVOhyscWDxpvRUEZdGQ0vxMkOEppT@mail.gmail.com>
Subject: Re: Domains, casts, and MS Access
From: Richard Broersma <richard.broersma@gmail.com>
To: Peter Koczan <pjkoczan@gmail.com>
Cc: pgsql-sql@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Aug 4, 2010 at 10:31 AM, Peter Koczan <pjkoczan@gmail.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