Re: [GENERAL] subselect field "problem"

[Thomas H.]

i was writing the query below containing a subquery. by mistake, i 
referenced a field from the main table in the subquery, leading to a 
very strange (but working??) result. the planner announced a insanely 
high startup cost, but the query itself finished pretty quickly.
    

Pick up any SQL book and read up on correlated subqueries.

Have a nice day,
  
thanks! i didn't knew this term. the result is pretty obvious now, and 
so is the high cost prediction.

regards,
thomas