no I don't. That's the problem. At any time it could be any random number of fields that come up empty. I know how to parse out the empty fieldnames in CF, I wanted to find a SQL solution cause I'm going to have to do this same thing for a lot of tables one right after the other and I wanted to shove off the processing to SQL server if I could. ----- Original Message ----- From: "Shawn Regan" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Wednesday, September 18, 2002 12:14 PM Subject: RE: Returning columns with null values when specific columns are unknown at runtime
> Do you know the fieldnames? Or is this something that has to be figured out > also? > > Shawn Regan > pacifictechnologysolutions > 15530-B Rockfield Blvd. Suite 4 > Irvine, CA 92618 > 949.830.1623 > w w w . p t s 1 . c o m > > > > -----Original Message----- > From: Patti G. L. Hall [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 18, 2002 8:56 AM > To: CF-Talk > Subject: Re: Returning columns with null values when specific columns > are unknown at runtime > > > Ok, I'm willing to give this a try... but I still have a question. > > My real table has 27 columns. I never know which columns will be null. > Does that mean I want a case statement for each column that could possibly > be null then? > > It seems like the select statment here is directly tailored to the example I > used below... I will never know that much detail beforehand. I only put the > example to give a visual of what I may need to return. > > If I send in primary key 1 then I want to return columns 3 and 4, but only > if they acutally are null. The next time I run the query I'd be sendign in > primary key 2 and in that case I'm returning columns 1, 3 and 4. > > So, I just wanted to check ... Can you explain how this is actually working? > Is it relying on my explictly stating which columns I'm returning at any one > time? If it is, then it's still not what I'm looking for. And perhaps what > I'm looking for isn't possible. > > Thanks - Patti > ----- Original Message ----- > From: "Jim Curran" <[EMAIL PROTECTED]> > To: "CF-Talk" <[EMAIL PROTECTED]> > Sent: Wednesday, September 18, 2002 11:26 AM > Subject: RE: Returning columns with null values when specific columns are > unknown at runtime > > > > SELECT CASE WHEN pk = 1 THEN col3 END AS newcol1, > > CASE WHEN pk = 1 THEN col4 END AS newcol2, > > CASE WHEN pk = 2 THEN col1 END AS newcol1, > > CASE WHEN pk = 2 THEN col2 END AS newcol2 > > FROM mytable > > > > > > -----Original Message----- > > From: Patti G. L. Hall [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, September 18, 2002 10:54 AM > > To: CF-Talk > > Subject: SQL: Returning columns with null values when specific columns > > are unknown at runtime > > > > > > Is there a way to write a MSSQL 2k query that will return a result set > that > > contains only columns with null values when you don't know explicitly > which > > columns those will be? > > > > So if I have this data > > > > pk | col 1 | col 2 | col 3 | col 4| > > 1 1 2 null null > > 2 null 4 null null > > > > I'd like a query that would return col 3 and col 4 where pk = 1 or col 1, > > col 3 and col 4 where pk=2. > > > > Is this possible? > > -Patti > > > > > > > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
