> You're probably right, but that doesn't speak to the > cause. I use > unions a _lot_ and would like to know that I'm using > them correctly. > It looks like I'll have to exclude "all" from the > union operator as a > matter of course.
My goal is to try to figure out where the problem is being introduced. If UNIONing two views, rather than two SELECTs, makes the problem go away, then there is probably some problem in the way the two SELECTs are written in context of a UNION SELECT (which could be a problem in the way you wrote the view, or could be something broken in the way the select is parsed). If it _doesn't_ cause the problem to go away, I would think that there is definitely something amiss in the internals which you would want to report to RDCC. -- Larry __________________________________________________ Yahoo! - We Remember 9-11: A tribute to the more than 3,000 lives lost http://dir.remember.yahoo.com/tribute ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
