Hi All, I have a view that is a series of 4 'union all' selects. One, and sometimes 2, duplicate all but 1 row. So, instead of 250 rows being returned, 499 are. If I issue the select independently I get the correct result. By rearranging the unions one select stopped duplicating (it became the first select).
I included a literal in the selects so I could clearly identify what was happening and did counts before and after to be sure I wasn't getting combinations from prior selects. I know I can use UNION rather then UNION ALL, but I don't want the performance hit of RBase trying to remove the dups (after it creates them????). I do this routinely and can't figure out what might be going on in this case. Of course, I've made sacrifices to the DB Gods, bloodied the wall next to my desk with my forehead, cursed, cried, and laughed maniacally... all for not. Has anyone else experienced this (the duplicating 'union all sel', that is <g>)? tia, Ben Petersen ================================================ 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/
