From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | nwalls(at)kyledavidgroup(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15907: JSON Select Issue |
Date: | 2019-07-16 04:49:56 |
Message-ID: | 20190716044956.GB19396@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Jul 15, 2019 at 08:17:13PM +0000, PG Bug reporting form wrote:
> I have a table that has a column named 'metadata' of type JSON. When I try
> to select metadata as part of a group with other columns, I've found that
> metadata has to be the first column selected. Otherwise I'll get an error
> saying "Not connected to the server or the connection to the server has been
> closed," even though a modal will still inform me the query was executed
> successfully with N number of rows affected. For example:
> SELECT metadata,kind FROM events; --works just fine
> SELECT kind,metadata FROM events; --fails
It would be surprising if this is a bug. Do you have a reproducible,
self-contained test case that shows the problem? Perhaps you have an
issue with your client application?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-07-16 06:01:47 | Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2 |
Previous Message | Saul, Jean Paolo | 2019-07-16 03:44:32 | Re: [BUG?] Missing OID column from pl/pgsql record |