| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marek Lewczuk <newsy(at)lewczuk(dot)com> |
| Cc: | Lista dyskusyjna pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Sequence name with SERIAL type |
| Date: | 2003-12-17 09:23:00 |
| Message-ID: | 26363.1071652980@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Marek Lewczuk <newsy(at)lewczuk(dot)com> writes:
> I'm curious if the default scheme for sequence name (which is created
> with SERIAL data type) can be changed -- currently all sequences are
> named like this: <table_name>_<field_name>_seq -- can it be changed for
> e.g. <table_name>__<field_name>__seq ???
Sure ... just hack one or two places in the sources ...
That probably wasn't the answer you wanted, but I'm quite unsure what
you did want. Are you suggesting the above would be a better default
naming scheme? Are you saying you want user-configurability of implicit
sequence names? In either case, what's your argument why we should
invest effort and possibly create backwards-compatibility issues?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2003-12-17 09:32:22 | Re: md5 function |
| Previous Message | Michael Fuhr | 2003-12-17 09:19:33 | Re: Sequence name with SERIAL type |