Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Broken\s+query\s+question\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Broken\s+query\s+question\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] Broken query question (score: 1): Author: "Huebschman, George J." <GJHuebschman AT LMUS.LEGGMASON DOT COM>; Date: Wed, 1 Oct 2008 15:09:18 -0400; Greetings everyone, I ran what I thought was a pretty simple SQL query, but I received (semi) garbage information back. I wanted to get slimmed down information like a QUERY SCHEDULE, to find out wha; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00009.html (13,154 bytes)
2. Re: [ADSM-L] Broken query question (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Wed, 1 Oct 2008 21:13:04 +0200; - I had expected that the paramater naming the node_name would limit the query to only the schedule associated to that node....and it did, partially. this is not correct, sql will do an 'outer join',; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00010.html (10,940 bytes)

Current List: 1 - 2
Page: [1]