From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | James Vinett <james(at)imdstrading(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Potential bug |
Date: | 2002-04-19 14:42:47 |
Message-ID: | 28047.1019227367@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
James Vinett <james(at)imdstrading(dot)com> writes:
> ERROR: TypeCreate: type bit already defined
This is neither a bug nor a keyword conflict.
A table has a datatype of the same name associated (the composite type
corresponding to its rowtype). So, when you try to create table "bit"
that means creating type "bit" too. But there already is one.
In 7.3 this issue will be considerably alleviated because the predefined
datatypes will live in a different schema (namespace) than user-defined
datatypes do. But you'll still get burnt if you make a datatype "foo"
and then try to create a table "foo".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-bugs | 2002-04-19 15:57:48 | Bug #636: REFERENCES on Inherits Table |
Previous Message | Tom Lane | 2002-04-19 14:37:56 | Re: Upgrade to 7.1.3 |