Along the lines of the equality operator; I have ran into issues trying to
pivot a table/result set with a json type due what seemed to be no equality
operator.
On Nov 4, 2013 10:14 AM, "Merlin Moncure"
>
wrote:
> On Fri, Nov 1, 2013 at 1:50 PM, Tom Lane
> >
> wrote:
> > Gregory Haase 'haa...
>Would help to include the explain(s). Did you ANALYZE after the insert; if
>not the planner probably still thought the table was empty (thus the
>matching explain) but upon execution realized it had records and thus
needed
>to run the CTE.
I did not do an ANALYZE after the insert, I think the pl
I thought this was interesting, and wanted to make sure I understood what
is going on, but the more tests I run the more confused I get.
if I take the exact set up outlined by Mosche I get the same results in 9.3
(as expected) , but if I insert one row before I run the sql the CTE is
executed and
http://kettle.pentaho.com/ works pretty good to.
On Mon, Oct 7, 2013 at 11:39 AM, Michal TOMA wrote:
> Talend?
> http://talend.com/
> But usually all major ETL tools do work with any database including
> PostgreSQL
>
> On Monday 07 October 2013 17:54:36 Vick Khera wrote:
> > http://lmgtfy.com/
I almost always alias my tables by default with something short (Usually 1
- 3 characters), but not my subselects for an in list. In this case I
would do d1, d2, ps, and p for the different tables. I then do my best to
use the same alias in all my queries. I am also big on formatting the SQL
h
