Adrian,
Working from my phone wasn't such a good idea!
When I said 'INSERT' I meant 'WITH'. My excuse is that the 'WITH' statement is
building a temporary table ( at least logically ) so there is at least an
implicit 'INSERT' there.
/s/jr
Sent from my iPhone
> On Jul 3, 2017, at 23:12,
Adrian,
Thank you for your reply!
I apologize in advance for not being detailed below. Hard to do from my phone.
I did have to move the 'ORDER BY', but not outside the 'WITH'. My first
workaround parenthesized the select containing the 'ORDER BY', forcing it to be
evaluated before the
On 07/03/2017 05:20 PM, Jerry Regan wrote:
Adrian,
Thank you for your reply!
I apologize in advance for not being detailed below. Hard to do from my phone.
I did have to move the 'ORDER BY', but not outside the 'WITH'. My first
workaround parenthesized the select containing the 'ORDER BY',
On 07/02/2017 10:33 AM, Jerry Regan wrote:
For reasons beyond my control, I am using Postgresql 9.4 on a MacBookPro
(development system). I use pgadminIII and psql for clients (I tried and
didn’t like the pgadmin4 UI; pg_dump, pg_restore also seem to be dumbed
down).
My question:
I have some
For reasons beyond my control, I am using Postgresql 9.4 on a MacBookPro
(development system). I use pgadminIII and psql for clients (I tried and didn’t
like the pgadmin4 UI; pg_dump, pg_restore also seem to be dumbed down).
My question:
I have some performance test results in table
