| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Kim Christensen | Date: | April 11 2006 10:56am |
| Subject: | Re: A complex JOIN scenario | ||
| View as plain text | |||
On 4/11/06, Santino <mc5422@stripped> wrote: > I do not try it : > > select invoice_id, order_id, customer_id, invoice_timestamp, > invoice_total, null > from invoice > union all > select invoice_id, null, null, null, null, invoice_journal_id > from invoice_archive Works like a charm, thanks! -- Kim Christensen kim.christensen@stripped
| Thread | ||
|---|---|---|
| • A complex JOIN scenario | Kim Christensen | 11 Apr |
| • Re: A complex JOIN scenario | Martijn Tonies | 11 Apr |
| • Re: A complex JOIN scenario | Kim Christensen | 11 Apr |
| • Re: A complex JOIN scenario | Martijn Tonies | 11 Apr |
| • Re: A complex JOIN scenario | Kim Christensen | 11 Apr |
| • Index merge optimization (with OR) and table joins | Stuart Brooks | 11 Apr |
| • Re: Index merge optimization (with OR) and table joins | sheeri kritzer | 4 May |
| • Re: Index merge optimization (with OR) and table joins | sheeri kritzer | 4 May |
| • Re: A complex JOIN scenario | Martijn Tonies | 11 Apr |
| • Re: A complex JOIN scenario | Kim Christensen | 11 Apr |
| • Re: A complex JOIN scenario | Santino | 11 Apr |
| • Re: Index merge optimization (with OR) and table joins | Stuart Brooks | 23 May |
| • Re: A complex JOIN scenario | Kim Christensen | 11 Apr |
| • Innodb import tuning on Sun T2000 | Russell Horn | 7 Jul |
