From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Arnaud Lesauvage <thewild(at)freesurf(dot)fr> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Access2000 & sequence as primary key in view : #DELETED |
Date: | 2006-10-12 02:27:57 |
Message-ID: | 452DA82D.9000701@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Arnaud Lesauvage wrote:
> Hi list !
>
> I created a view in postgresql (quite complex, multiple tables are
> linked). The aim is to link it in acces via ODBC.
>
> In needed to auto-number the rows, and I created a sequence for that
> (thanks to a good advice on the GENERAL list).
>
> In Access, I know that I need good primary keys on my linked tables
> (integer, single column). I though that using this column as a primary
> key would be a good idea .
>
> The view looks like this :
> CREATE OR REPLACE VIEW my_view AS
> SELECT nextval('my_view_seq'::regclass)::integer AS "index", <many
> other fields> FROM <many tables>;
Though I don't understand the problem wholly, the virtual column "index"
doesn't seem appropriate for the identifier. How do you find the row
using the "index" ?
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Mijatovic | 2006-10-12 05:53:40 | Redhat odbc configuration help |
Previous Message | noreply | 2006-10-12 02:14:21 | [ psqlodbc-Bugs-1000749 ] Crashes when using SSL with 8.02.0002 and .0100 |