"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Andrew Sullivan" <[EMAIL PROTECTED]> writes:
>>> I would say just set up a project on pgfoundry.
>
>> I agree, though I think in the long term we do need a more complete set of
>> operators and functions in cor
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Andrew Sullivan" <[EMAIL PROTECTED]> writes:
>> I would say just set up a project on pgfoundry.
> I agree, though I think in the long term we do need a more complete set of
> operators and functions in core.
Considering that BIT and BIT VARYING have b
"Andrew Sullivan" <[EMAIL PROTECTED]> writes:
> On Mon, Jul 16, 2007 at 09:40:18AM -0700, TJ O'Donnell wrote:
>> I would like to make these a part of postgresql for others to use.
>> Is it more appropriate for these to be in contrib code
>> or part of the postgresql proper?
>> How can I contribut
On Mon, Jul 16, 2007 at 09:40:18AM -0700, TJ O'Donnell wrote:
> I would like to make these a part of postgresql for others to use.
> Is it more appropriate for these to be in contrib code
> or part of the postgresql proper?
> How can I contribute these?
I would say just set up a project on pgfound
I have been working extensively with the bit string data type.
I have a number of useful c-language functions to
set/clear a bit, count number of bits set, inquire if
a bit is set/clear, etc.
I don't see functions like these as part of any SQL standard,
(although I think they ought to be).
I woul
