Is there a way to pass in the entire WHERE clause as a parameter?
yeah, but then there's no point in using a stored procedure, because the
advantage of the stored procedure is that the database can figure it out
ahead of time (compile it, as it were), and if the retrieval condition
columns are
-
From: rudy [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 07, 2003 3:04 PM
To: [EMAIL PROTECTED]
Subject: [wdvltalk] Re: StoredProcedures
Is there a way to pass in the entire WHERE clause as a parameter?
yeah, but then there's no point in using a stored procedure, because the
advantage
On Friday, February 7, 2003 at 23:16, Bill Mais wrote:
BM It makes sense the sp can only be compiled if it is complete.
the stored procedure will be compiled, but will be recompiled on each use
as the sql changed. this means that the database can't use the execution
plan it has calculated for
It makes sense the sp can only be compiled if it is complete.
actually, it can be compiled as long as it has some idea of what will happen
for example,
WHERE foo = @param
the compiler knows that a value will be substituted at run time
it knows that foo has an index, so it knows it can
Working late, rudy? Or is it early in your neighbourhood?
Sherry from New Hampshire (11:30 EST)
rudy wrote:
Is there a way to pass in the entire WHERE clause as a parameter?
yeah, but then there's no point in using a stored procedure, because the
advantage of the stored procedure is that
