From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Binary data type with other output method |
Date: | 2007-12-26 01:36:23 |
Message-ID: | 4771B017.60501@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> I think all you need to do it this:
>> Take the code for boolout() in src/backend/utils/adt/bool.c, adjust it
>> and and make it a new function boolout2. Use pgxs to make it a loadable
>> module.
>> Then load it and adjust the catalog entry for the bool type to use
>> boolout2 instead of boolout.
>>
>
> Then start fixing pg_dump, psql, and every other bit of client-side code
> that expects the boolean columns in the system catalogs to read out as
> 't'/'f' ...
>
hmm, good point. Oh, well.
> I think you'd really need a separate type. But have you considered
> something simple like
> CREATE DOMAIN boolint AS int CHECK (value = 0 OR value = 1)
>
>
Of course, that's not exactly what he asked for. Maybe we need to know
more about the case.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas 'ads' Scherbaum | 2007-12-26 17:18:22 | Re: Binary data type with other output method |
Previous Message | Tom Lane | 2007-12-26 01:11:45 | Re: Binary data type with other output method |