Restart increment to 0 each year = re-invent the sequences mecanism ?

From: Bruno Baguette <pgsql-ml(at)baguette(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Restart increment to 0 each year = re-invent the sequences mecanism ?
Date: 2004-04-26 09:21:19
Message-ID: 408CD48F.3020101@baguette.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

I have to design a table wich will store some action reports. Each
report have an ID like this 1/2004, 2/2004, ... and each years, they
restart to 1 (1/2004, 1/2005, 1/2006,...).

So, I was thinking to split that in two fields : one with the increment
and one with the year. But I don't know how can I manage the sequences
since I have to restart to 0 each year...

Do you think I should re-invent the sequences mecanism with a second
table and a stored procedure, only to manage theses 'home-made' sequences ?

Or should I create some sequences like myseq_2004, myseq_2004,
my_seq_2005,... and use a concatenation of the myseq_ string and the
current year when calling nextval and curvall ?

Or is there another way to do that ?

Thanks in advance :-)

--
Bruno Baguette - pgsql-ml(at)baguette(dot)net

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Juris Krumins 2004-04-26 09:35:31 Re: cache lookup of relation 165058647 failed
Previous Message wespvp 2004-04-26 05:25:36 Re: thread_test.c problems