Quick HOWTO - connecting StarOffice Win or Lin to PostGreSQL using ODBC

We have had some problems to enable connection between StarOffice (on
GNU/Linux and on Windows systems) to a PostGreSQL database (running on
GNU/Linux) over ODBC connection.

Here is a quick howto I wrote as a reminder of the problems and
solutions we found.

Hope you find it useful.

Regards,

$Id: ConfigurationOdbc,v 1.2 2001/06/26 12:51:53 oberger Exp $

We have encountered problems to enable access to a GNU/Linux server
running PostGreSQL, from Linux and Windows platforms, both using
StarOffice? to access the database (using de StarBase? forms and
reports).

Our goal was to be able to interoperate with the database (read and
write) from both platforms in a unified way (same forms, look and feel).

The database connectivity from StarOffice? is made with ODBC.

StarOffice? configuration to access ODBC data sources is quite the same
once the ODBC sources have been defined.

We use the following ODBC drivers :

        unixodbc 2.0.4 for GNU/Linux, from http://www.unixodbc.org/
(package Debian 2.0.4-0.potato3)
        psqlodbc 7.1.0005 for Windows, from http://odbc.postgresql.org/
(zip file)


Problems encountered

The unixodbc driver, as packaged with the debian distribution does not
include a "default" /usr/lib/libodbcpsql.so file. Thus you have to
specify
the right libodbcpsql.so.* file in the .odbc.ini or odbc.ini /
odbcinst.ini files or create the appropriate link. See below.

The tables must have a primary key defined with a consttraint or index
in PostGreSQL in order to allow read-write access to the table from
StarOffice?.

The tables indices for primary keys must be named according to the
following scheme in order to be recognized by the PsqlODBC ODBC driver
for windows : "{table}_pkey" (see the FAQ
http://www.ca.postgresql.org/ftpsite/odbc/faq.html#primarykeys)

Configuring the PostGreSQL DataBase? server

The file pg_hba.conf should specify that PostGreSQL network access is
allowed from the client machines and users.

The postmaster.init file should include the option allowing network
connection (and be launched with -i option)

  PGALLOWTCPIP=yes


Configuring the GNU/Linux ODBC driver to allow access to the remote
server

We configured the .odbc.ini file with :

  [ODBC Data Source]
  funnel                  = funnel

  [funnel]
  Description            = FUNNEL satanas
  Driver            = /usr/lib/libodbcpsql.so
  Trace            = No
  Database            = template1
  Servername            = servername.domain.com
  UserName?            = postgres
  Password            = postgres
  ReadOnly?            = No


Beware that the library /usr/lib/libodbcpsql.so exist. If not, create a
link to the appropriate libodbcpsql.so.* file.

Configuring the Windows ODBC driver to allow access to the remote server

You should verify that the Read-Only checkboxes aren't checked in the
configuration option dialogs of the driver.

Creating tables structure

If you want to allow read-write access to the tables from StarOffice?
via the windows ODBC PostGreSQL driver, tables must have a primary
key named "{table}_pkey" (see the FAQ
http://www.ca.postgresql.org/ftpsite/odbc/faq.html#primarykeys)

By default, it will be OK if you create the table like this :

  CREATE SEQUENCE "table_seq";

  CREATE TABLE mytable (
          "id" INTEGER PRIMARY KEY DEFAULT NEXTVAL('table_seq'),

  ...
  );


If you use a CONSTRAINT definition, you should pay attention to the name
of the constraint :

  CREATE SEQUENCE "table_seq";

  CREATE TABLE mytable (
          "id" INTEGER DEFAULT NEXTVAL('table_seq'),

  ...

          CONSTRAINT "mytable_pkey" PRIMARY KEY("id")
  );

--
Olivier BERGER                          IDEALX S.A.S.
Développeur senior                      15-17, av. de Ségur
01.44.42.00.00                          F-75007 PARIS
06.81.27.86.79                          http://IDEALX.com/