Skip site navigation (1) Skip section navigation (2)

calculated identity field in views, again...

From: "Zlatko Matic" <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr>
To: <pgsql-general(at)postgresql(dot)org>, <pgsql-interfaces(at)postgresql(dot)org>
Subject: calculated identity field in views, again...
Date: 2005-05-03 22:04:41
Message-ID: 001201c5502c$1c030430$2d8b1dc3@zlatkovyfkpgz6 (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-interfaces
I asked this question several weeks ago, but nobody proposed a solution, so 
I am repeating the same question again...
I have an MS Access front-end for a database on PostgreSQL.
I could use pass-through queries as record sources for reports and it works 
Unfortunately, MS Access doesn't allow pass-through queries to be records 
sources for subforms.
Therefore I tried to base subforms on regular JET queries on linked tables. 
It was too slow...
Then I tried to base subforms on DAO recordset code generated from 
pass-through QueryDef objects. Although it worked, it was very unstable...

Now it seems to me that POstgreSQL views are the best solution, but Access 
considers views as tables (!) and needs column with unique values.
All those views are complicated queries on several tables, so I can't use 
any table's column as primary key. I need a calculated column in the view 
that Access will consider as primary key column.
In regular tables, I use bigserial field, but how can I create calculated 
bigserial column in a view ?


In response to


pgsql-interfaces by date

Next:From: Keith WorthingtonDate: 2005-05-04 03:58:28
Subject: Re: [INTERFACES] calculated identity field in views, again...
Previous:From: Thomas HallgrenDate: 2005-05-03 21:19:43
Subject: Re: Deep integration of PostgreSQL with Apache

pgsql-general by date

Next:From: CSNDate: 2005-05-03 22:06:37
Subject: Re: plpythonu and dollar quoting
Previous:From: Mohan, RossDate: 2005-05-03 21:51:38
Subject: Re: Favorable Postgresql write up

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group