At 09:28 AM 08/02/2001 -0400, you wrote:
> > Also, its better practice to build your where clause outside
> > of the CFQUERY.
>
>Out of curiosity, what's the reason for this?
I'm jumping in during the middle of this conversation, so bear with me.
If I understand correctly, I have heard this b
> Also, its better practice to build your where clause outside
> of the CFQUERY.
Out of curiosity, what's the reason for this?
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~
Structure your
How about creating a view in SQL Server that shows all the data without the
Where clause, then you can just :
select your, fields from theview where whatever
It'll save you from doing all the joins over and over again in CF and it'll
be optimised by SQL Server, all you have to worry about is you
sorry, not quite awake yet...
-Original Message-
From: BT [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 02, 2001 9:03 AM
To: CF-Talk
Subject: RE: Dynamic Stored Procedure
Somehow my SQL Statement go cut off but we have select blah blah
do this order by your momma
See what I mean
Somehow my SQL Statement go cut off but we have select blah blah
do this order by your momma
See what I mean
-Original Message-
From: Stuart Miller [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 02, 2001 4:03 AM
To: CF-Talk
Subject: RE: Dynamic Stored Procedure
>I was wondering
>I was wondering if there is a way in SQL on SQL7 to say if this variable is
>passed the add a where clause or something..
You can try SQL CASE statements. You will, of course, have to declare the
variables you need in the stored procedure. I have found some performance
issuses with using dy
6 matches
Mail list logo
