Re: currval() without specifying the sequence name

From: Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: ow <oneway_111(at)yahoo(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: currval() without specifying the sequence name
Date: 2004-03-09 15:09:47
Message-ID: Pine.LNX.4.44.0403091705490.32587-100000@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

O kyrios ow egrapse stis Mar 9, 2004 :

>
> --- Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> wrote:
> >
> > You could use the same sequence in many tables.
> >
>
> I guess I could but then:
>
> 1) I'd still have to know the sequence name. When integrating pgSql with 3party
> frameworks I'd either have to pass it there (could be a very difficult task) or
> make some assumptions (also not very good).
>
> 2) There may be a need to have different sequences being used in an app.
>
> 3) If one sequence is used, in many cases it'll have to be of type int8 and
> pgSql does not handle searches with int8 very nicely.
>
> Thanks
>
>

I dont think you have given solid reasons as to why somebody whould
want to do that (in order to be more specific and help you better),
but in any case:

foodb=# SELECT relname from pg_class where relkind = 'S';
relname
---------------
footbl_id_seq
footbl2_id_seq
(1 row)

gives you a list of sequences of your current schema.

Then you can loop thru those to:

select last_value from <cur_seq>;
and get the maximum, but again what exaclty are you trying to do?

>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Search - Find what you’re looking for faster
> http://search.yahoo.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

--
-Achilleus

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Richard Huxton 2004-03-09 15:14:56 Re: currval() without specifying the sequence name
Previous Message Michael Glaesemann 2004-03-09 14:58:35 Re: Trying to make efficient "all vendors who can provide all items"