Postgresql – Need ODBC connection to postgresql to include materialized views

materialized-viewms accessodbcpostgresql-9.4

I have an Access front end user interface that links to tables in a postgreSQL database using the most recent ODBC driver. I can link to the postgreSQL tables and views but can't get to the materialized views.

This thread describes a patch to the driver to include materialized views. Does anyone know if this patch is included in the most recent driver? If not, how would I apply it? If it is included, which options need to be selected so that materialized views are accessible from MS Access?

Best Answer

I have found that Postgres views are included in the linked tables within Access. Click on any linked table within Access and within the list should be your views. I always find it useful within Postgres to preface a view name with 'VIEW_' so that they are all readily visible and accessible within Access.

Related Solutions

Ms-access ODBC calls for linked table behaviour

The only way to get complete control over the query for ODBC is to create them as pass-through queries.

In that mode, Access will not touch them and the SQL will be passed verbatim to the server (so your queries will need to be written in that server's particular SQL syntax or you'll get errors).

In ODBC mode, Access will decompose queries that are bound to controls into batches so it never returns more results than it need to display (that is what you see: it will decompose queries based on the primary key to return specific records only).

So you have to be careful of what you wish: if you optimise your queries using pass-through, you will get less calls, but all the data will be returned.

On the other hand, if you leave Access do the querying for you, it may be chattier, but the net performance may be better since less data may be returned more quickly.

You need to test both and choose what works best depending on the exact query and how it is used.

Postgresql – limit access to postgresql 8.4 databases via ODBC on the server side

ODBC is a client tool and does not affect the way that Postgresql verifies access. I don't know if its any different for a postgresql server on windows, but in linux, there is a file called pg_hba.conf. This file is usually located in the data directory of the server install. In Linux, you typically find it in /var/lib/pgsql/data/.

This file allows you to define which ip addresses can access your postgresql server and how they may access it. Types of access include trust (no password), md5 (password), etc.

So for example, if your access users are on say 192.168.0.10 and you want them to use a password you would add this entry.

# TYPE  DATABASE    USER        IP-ADDRESS    IP-MASK             METHOD
host    all         access_user         192.168.0.10    255.255.255.255     md5

In postgresql you would then have to create the user and give him the ability to login.

1. psql -d nameofdatabase
2. CREATE ROLE access_user WITH LOGIN PASSWORD 'jw8s0F4';
3. GRANT SELECT ON nameoftable TO access_user;

Good luck

Best Answer

Related Solutions

Ms-access ODBC calls for linked table behaviour

Postgresql – limit access to postgresql 8.4 databases via ODBC on the server side

Related Question