Thread: info schema : cardinal number domain

info schema : cardinal number domain

From
elein
Date:
When creating a table with a bit type
of length less than 4, then any selection
to the information.schema.columns table
that hits that row gives the following error:

drop table infoschema_bit;
create table infoschema_bit (
   bitcol bit(3)
);
select * from columns;

-- ERROR:  value for domain cardinal_number violates check constraint "cardinal_number_domain_check"

There may be other places where this hits.
I ran into it creating an "alltypes" table for
an example and just grabbed the bit(3) from the
documentation on the bit type.

This is relatively low priority as I suspect
few people use both the information schema AND
small bit types right now.

elein@varlena.com

Re: info schema : cardinal number domain

From
Tom Lane
Date:
elein <elein@varlena.com> writes:
> When creating a table with a bit type
> of length less than 4, then any selection
> to the information.schema.columns table
> that hits that row gives the following error:
> -- ERROR:  value for domain cardinal_number violates check constraint "cardinal_number_domain_check"

This is fixed as of 7.4.1, along with several other information_schema
bugs.  If you have a database that was initdb'd under 7.4, you can load
the corrected views without re-initdb'ing: as superuser, DROP the
information_schema and execute the updated information_schema.sql file
(look in $INSTALLDIR/share).

            regards, tom lane

Re: info schema : cardinal number domain

From
elein
Date:
oops. I need to update to 7.4.1.
Thank you.

--elein

On Sat, Jan 31, 2004 at 07:26:38PM -0500, Tom Lane wrote:
> elein <elein@varlena.com> writes:
> > When creating a table with a bit type
> > of length less than 4, then any selection
> > to the information.schema.columns table
> > that hits that row gives the following error:
> > -- ERROR:  value for domain cardinal_number violates check constraint "cardinal_number_domain_check"
>
> This is fixed as of 7.4.1, along with several other information_schema
> bugs.  If you have a database that was initdb'd under 7.4, you can load
> the corrected views without re-initdb'ing: as superuser, DROP the
> information_schema and execute the updated information_schema.sql file
> (look in $INSTALLDIR/share).
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend