From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Olivier Berger <olivier(dot)berger(at)idealx(dot)com>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Write access problems with StarOffice for Windows |
Date: | 2001-06-27 05:36:42 |
Message-ID: | 3B3970EA.6487EABA@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Olivier Berger wrote:
>
> Olivier Berger wrote:
> >
> > Hello.
> >
> > I'd like to know if anyone has ever experienced the same problem :
> > we've setup an ODBC connection with the PostgreSQL ODBC driver from
> > windows to a PostgreSQL Database (the server is on GNU/Linux).
> >
> > The database can be accessed in read/write with MSQuery and MSAccess,
> > but in read-only with StarOffice.
> >
> > Has anyone experienced any incompatibility with StarOffice ?
> >
>
> Well, we seem to have found a solution.
>
> The problem comes from a naming scheme problem with the postgresql ODBC
> driver for windows or StarOffice windows interpretation of primary key
> indices.
>
> If we name the primary index of our [my_table_name] table whith
> "[my_table_name]_pkey", it apparently solves our problems, and the
> tables can be accessed from StarOffice with write access.
>
Recently I changed the driver so that it detects the primary
key other than {table_name}_pkey. Please try the next release
(7.01.0006). It would be released in a week or so.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2001-06-27 08:07:34 | an ODBC change |
Previous Message | Olivier Berger | 2001-06-26 13:14:14 | Quick HOWTO - connecting StarOffice Win or Lin to PostGreSQL using ODBC |