Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for? - Mailing list pgsql-general

From Dennis Jenkins
Subject Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for?
Date
Msg-id CAAEzAp8PpDur=kVrPZYmbJxUTrMLEA0w3Y7bUXZwJz_oYMD-Aw@mail.gmail.com
Whole thread Raw
In response to Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for?
List pgsql-general

On Fri, May 22, 2015 at 10:02 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Alban Hertroys <haramrae@gmail.com> writes:
> On 22 May 2015 at 04:46, Bill Moran <wmoran@potentialtech.com> wrote:
>> With all that being said, if I were to build a patch, would it be likely
>> to be accepted into core?


How feasible would it be to write a network proxy, like pg_bouncer, to handle converting the values on the fly, so that you need to change neither your original code base (with respect to this issue), nor change PostgreSQL itself?

pgsql-general by date:

Previous
From: Gilles Darold
Date:
Subject: Re: date with month and year
Next
From: Bill Moran
Date:
Subject: Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for?