Guyren Howe writes:
> Thanks. This is… inconvenient. I see nothing about an option to force quoting
> of strings. Is there no such option? If not, I suggest that it would be a
> useful addition.
Force-quoting the elements would not move the goalposts all that much
concerning parse-ability of co
On Monday, May 15, 2017, Tom Lane wrote:
> Guyren Howe > writes:
> > ... get this result:
> > (200,{},Works!)
> > This is the textual representation of the result I get in psql and Ruby.
> Note that the textual final value is not quoted.
> > I imagine I can work out a way to deal with this, but t
> On May 15, 2017, at 21:36 , Tom Lane wrote:
>
>> ... get this result:
>> (200,{},Works!)
>> This is the textual representation of the result I get in psql and Ruby.
>> Note that the textual final value is not quoted.
>> I imagine I can work out a way to deal with this, but this is not the mos
Guyren Howe writes:
> ... get this result:
> (200,{},Works!)
> This is the textual representation of the result I get in psql and Ruby. Note
> that the textual final value is not quoted.
> I imagine I can work out a way to deal with this, but this is not the most
> felicitous way of representing
Define a couple of types:
CREATE TYPE request_in AS
(
path text[],
args jsonb,
server text,
port smallint,
headers jsonb,
body bytea,
type_requested text[]
);
CREATE TYPE request_out AS
(
status smallint,
headers jsonb,
