|
|
Posted by cphite on 09/07/06 21:34
Erland Sommarskog wrote:
> (cphite@gmail.com) writes:
> > There are a lot of reasons someone might want to create a table on the
> > fly. They might want to store a snapshot of data at a given time that
> > is easily accessable. It may not fit your ideal of how SQL "should" be
> > used, but it's actually quite common in the real world - and it need
> > not invoke images of falling pachyderms.
>
> Yes, temp tables are a fair game, but dynamically named tables isn't.
> If nothing else, because it's completely painful to work with them.
>
> Reading the original post again, I think the real solution that Pukivruki
> needs is a permanent table keyed by a process id. Often @@spid can be
> used as key, but in this case @TICKET may be a better choice.
Well, personally I agree with you for his case - but there is a
difference between telling someone there is a better way of doing
something, and getting all in their face with this "Not in an RDBMS!"
nonsense. There is a difference between trying to help someone out,
and trying to use the newsgroup as a means to work out your personal
insecurities by berating someone who asks a simple question.
Plus, I'm just bored today so... :b
Navigation:
[Reply to this message]
|