Re: Domains, casts, and MS Access - Mailing list pgsql-sql

From Richard Broersma
Subject Re: Domains, casts, and MS Access
Date
Msg-id AANLkTikrAF5hJ24dQVK6OPHMq=_i1Qv5Bi73rDP8U0WM@mail.gmail.com
Whole thread Raw
In response to Re: Domains, casts, and MS Access  (Peter Koczan <pjkoczan@gmail.com>)
Responses Re: Domains, casts, and MS Access  (Peter Koczan <pjkoczan@gmail.com>)
List pgsql-sql
On Wed, Aug 4, 2010 at 3:41 PM, Peter Koczan <pjkoczan@gmail.com> wrote:

> Yep, that's the stumbling block we're running into. ODBC and these
> fields' assumptions of true/false are at odds. I'm trying a few other
> things with casts in the meantime to see if they'll work.

Well there is a solution that I've been toying around with.  In
PostgreSQL, there are many data-types that cannot be expressed
directly in an MS-Access Linked table.  For example, composite types,
arrays, range types, hstores, postgis types et.al.   However, most of
these types can be decomposed in to base types that can be express in
linked tables.

The key is using update-able views to decompose the data for Access
and re-assemble it before it transmitted back to the base table.  The
same can be done for boolean datatype.


> Does anyone know if another product, like OpenOffice Base with its
> native postgres driver, does any better?

From my limited experience, I believe is does do better.  The
following blogs as a few entries about using Base:

http://www.postgresonline.com/journal/archives/167-Importing-data-into-PostgreSQL-using-Open-Office-Base-3.2.html


-- 
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug


pgsql-sql by date:

Previous
From: Peter Koczan
Date:
Subject: Re: Domains, casts, and MS Access
Next
From: David Bolen
Date:
Subject: Re: Domains, casts, and MS Access