"Chad Attermann" <[EMAIL PROTECTED]> wrote: > I am using HIGH_PRIORITY in my SELECTs to force queries to take predcedence over > updating > due to replication. I have recently implemented UNION in some of my queries to > optimize > queries like "WHERE table1.column1=something OR table1.column2=somethingelse". > > Anyway, I first tried formatting my UNION query like "(SELECT HIGH_PRIORITY ...) > UNION > (SELECT HIGH_PRIORITY ...)" but the server complained about the placement of > HIGH_PRIORITY. I was finally able to get it to accept the query by only specifiying > HIGH_PRIORITY in the first part of the UNION, like "(SELECT HIGH_PRIORITY ...) UNION > (SELECT ...)", but it appears that my searches are not taking precedence as they > should, > and as non-UNION queries do. Could there be another explanation for why they are not > taking precedence, or is there another way to specify HIGH_PRIORITY in UNION queries > to > make both sub-queries high-priority?
You can specify HIGH_PRIORITY in the first SELECT statement, but you are right HIGH_PRIORITY doesn't take any effect in queries with UNION. Thank you for bug report! -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
