| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Kirk Wolak <wolakk(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, ailjushkin(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: nextval parameter is not clear |
| Date: | 2022-11-28 05:45:28 |
| Message-ID: | 452493.1669614328@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> Now I think that is taking it too far. Your code sample would be great
> for a tutorial, but it is too elaborate for the technical documentation.
> The example should focus on the sequence functions, but more than half
> of the code describes other parts of PostgreSQL:
Yeah, that stuff seems quite out of place here.
> I am alright with having a CREATE TABLE with a DEFAULT and an INSERT or two;
> whatever it takes to show the functions in a realistic scenario.
> For example, you could INSERT a row that overrides the DEFAULT, then call
> "setval()" to readjust the sequence.
I don't believe we have such detail around very many, if indeed any,
of our other functions' documentation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2022-11-28 10:20:05 | Re: temporary file size clarification |
| Previous Message | Laurenz Albe | 2022-11-28 03:34:56 | Re: nextval parameter is not clear |