Re: Pass a variable into procedure to use as column in select statement

sybrandb_at_hccnet.nl wrote:
> On Thu, 3 Apr 2008 12:11:43 -0700 (PDT), OutCast
> <Joe.r.rhea_at_jpmchase.com> wrote:
>
>> Thanks, problem solved. I added the two new table and it worked
>> perfectly, plus i'll store the knowledge of the "execute immediate"
>> for when I really need it. It is amazing how doing it right always
>> makes things so much easier.
>
> Actually you still don't do it right. You have a denormalized table
> design, and in order to get around this you are using dynamic sql,
> which makes your app unscalable.
> Hopefully there will never be someone who has to clean out the mess
> you left.

Hmm, I'm not sure but phrases like "I added the two new table(s)" and "I'll store the knowledge of the "execute immediate" for when I really need it" seem to suggest he followed your earlier advice to normalize in favor of using dynamic sql with "execute immediate".

Cheers!

-- 
Jeroen