| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | create composite type error message |
| Date: | 2010-01-18 23:49:49 |
| Message-ID: | 1263858589.24310.7.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
When you create a composite type that already exists, the error message
you get is about 'relation "foo" already exists'. While true, this can
be confusing, as you didn't plan to create a relation. Therefore, I
propose that we insert a snippet of code that is already used by the
other forms of type creation to check first whether a *type* with that
name exists.
| Attachment | Content-Type | Size |
|---|---|---|
| create-composite-type.patch | text/x-patch | 1.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kurt Harriman | 2010-01-19 00:34:48 | Re: Patch: Remove gcc dependency in definition of inline functions |
| Previous Message | Kevin Grittner | 2010-01-18 23:25:03 | Re: Review: Patch: Allow substring/replace() to get/set bit values |