Re: increment counter in VIEW

Dear All,
Thank you very much for your answers. I just want to summarize:
1. create sequence:
CREATE SEQUENCE myseq;

2. insert sequence function calls into VIEW:
CREATE OR REPLACE VIEW my_view AS SELECT
nextval('myseq')::text AS test,
knoten.knoten,
FROM
setval('myseq',1),
knoten knoten
WHERE
knoten.knoten::text = knoten_flaeche.knoten::text;

In Postgres it seems to work fine, but not yet in my application.
My doubt is about setval('myseq',1). I am not sure that it will always
works fine when I access view from my application. For example when I
call on_update rule.

Oleg

Oleg schrieb:
> Dear Richard,
> Thank you very much for your link. It looks like it could do the job I
> want.
> Unfortunately I have problem with inserting this functionality into my
> VIEW
> I tried:
> CREATE OR REPLACE VIEW my_view AS SELECT
> S.a AS test,
> knoten."GEOMETRY",
> knoten.knoten,
> FROM
> generate_series(1,300) AS S(a),
> knoten knoten
> WHERE
> knoten.knoten::text = knoten_flaeche.knoten::text;
>
> Without generate_series my View produces 300 records. if I insert
> generate_series then I get 90000 because it tries all possible
> combinations with S.a. I do not know how can I limit it with WHERE.
>
> I also tried to work with SEQUENCES but each time we update sequence
> it continue to count from the last number. For example from 1-300 then
> from 300-600, etc.
>
> We would be very grateful if you or somebody on this list could help
> us further.
>
> Thanks a lot in advance,
> Oleg
>
>
> Richard Broersma Jr schrieb:
>>> Dear All,
>>> Does anybody know how to add increment counter column to VIEW? To
>>> get something like this
>>>
>>> cntrColumn | anotherCol
>>> ------------------------
>>> 1 | val1
>>> 2 | val2
>>> 3 | ..
>>> 4 |
>>>
>>> The best if this counter will be executed together with sort to
>>> ensure that sertain record gets always the same Counter value.
>>>
>>
>> I am not sure if generate_series is what you want.
>> http://www.postgresql.org/docs/8.1/interactive/functions-srf.html
>>
>> Regards,
>> Richard Broersma Jr.
>>
>>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>