Re: [GENERAL] calculated identity field in views, again...
От | Zlatko Matic |
---|---|
Тема | Re: [GENERAL] calculated identity field in views, again... |
Дата | |
Msg-id | 001801c55087$2828d9a0$c5861dc3@zlatkovyfkpgz6 обсуждение исходный текст |
Ответ на | calculated identity field in views, again... ("Zlatko Matic" <zlatko.matic1@sb.t-com.hr>) |
Ответы |
Re: calculated identity field in views, again...
|
Список | pgsql-interfaces |
I will try...if it will be useless, I will quite. Then the only solution will be make-table query based on nested pass-through query, so I will be working on local JET tables that will be refreshed from server on each session. But I would like to avoid local tables, if possible... How do I create sequence ? ----- Original Message ----- From: "Greg Stark" <gsstark@mit.edu> To: "Zlatko Matic" <zlatko.matic1@sb.t-com.hr> Cc: <pgsql-general@postgresql.org>; <pgsql-interfaces@postgresql.org> Sent: Wednesday, May 04, 2005 7:11 AM Subject: Re: [GENERAL] [INTERFACES] calculated identity field in views, again... > "Zlatko Matic" <zlatko.matic1@sb.t-com.hr> writes: > >> In regular tables, I use bigserial field, but how can I create calculated >> bigserial column in a view ? > > You would have to create a sequence and reference it with > nextval('sequencename') in your view. But I doubt very much that it will > do > anything useful. > > It sounds like Access wants to be able to update records by looking them > up by > primary key. In that case assigning a new value in your view will make > Postgres make up a brand new number that is utterly useless for finding > the > record again later. > > -- > greg > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >
В списке pgsql-interfaces по дате отправления: