Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for?

From: Dennis Jenkins <dennis(dot)jenkins(dot)75(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for?
Date: 2015-05-22 16:27:49
Message-ID: CAAEzAp8PpDur=kVrPZYmbJxUTrMLEA0w3Y7bUXZwJz_oYMD-Aw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, May 22, 2015 at 10:02 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Alban Hertroys <haramrae(at)gmail(dot)com> writes:
> > On 22 May 2015 at 04:46, Bill Moran <wmoran(at)potentialtech(dot)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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2015-05-22 16:34:04 Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for?
Previous Message Tom Lane 2015-05-22 15:02:47 Re: Allowing postgresql to accept 0xff syntax for data types that it makes sense for?