Only if you want to see duplicate rows :-)
On Tue, Aug 17, 2010 at 2:21 PM, Ananda Kumar wrote:
> use UNION ALL ..instead of UNION for better performance...
>
> On Tue, Aug 17, 2010 at 5:01 PM, Johan De Meersman >wrote:
>
> > You may want to split of your or conditions into a separate query, an
use UNION ALL ..instead of UNION for better performance...
On Tue, Aug 17, 2010 at 5:01 PM, Johan De Meersman wrote:
> You may want to split of your or conditions into a separate query, and use
> UNION.
>
> On Tue, Aug 17, 2010 at 11:22 AM, Влад Р wrote:
>
> > The main problem - if add in Join o
You may want to split of your or conditions into a separate query, and use
UNION.
On Tue, Aug 17, 2010 at 11:22 AM, Влад Р wrote:
> The main problem - if add in Join on `OR`-condition, select become
> VERY slow. I realy
> have to use this condition.
>
> -- ---
The main problem - if add in Join on `OR`-condition, select become
VERY slow. I realy
have to use this condition.
--
--
-- `tree_data`
--
CREATE TABLE IF NOT EXISTS `tree_data` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`pid` int(11) NOT N
i solved the problem...
for the ones, who wants to know:
only creating an index on artikelnummer on both tables made the query
beeing ready after 2 seconds again :-)
Oliver
On Wed, 15 Sep 2004 00:38:59 +0200, Oliver Schiessl
<[EMAIL PROTECTED]> wrote:
MySQL 3.23.58:
ive got 2 tables with ca.
MySQL 3.23.58:
ive got 2 tables with ca. 3 entrys each
now i wanna join, if one entry is in the one table, which isnt in the
other one
so this will be a normal join:
Tabelle1:
Artikelnummer, blah, blah, blah
Tabelle2:
Artikelnummer, blah, blah, blah
select Tabelle1.Artikelnummer from Tabelle
Don Read wrote:
>
> On 11-Jul-01 Mike W. Baranski wrote:
> > Awsome answers! I'll clear a few things up where appropriate
> >
> > Don Read wrote:
>
>
>
> >>
> >>
> >> Why the LEFT JOINS ?
> >> They're (mostly) used for finding set membership; whenever you see
> >> 'LEFT JOIN b' without s fo
On 11-Jul-01 Mike W. Baranski wrote:
> Awsome answers! I'll clear a few things up where appropriate
>
> Don Read wrote:
>>
>>
>> Why the LEFT JOINS ?
>> They're (mostly) used for finding set membership; whenever you see
>> 'LEFT JOIN b' without s following 'b IS [NOT] NULL' clause 'tis t
Awsome answers! I'll clear a few things up where appropriate
Don Read wrote:
>
> On 11-Jul-01 Mike Baranski wrote:
> > I was wondering if anyone had any suggestions on the following problem. I
> > have a table with about 7 million rows, and I'm using the following
> > join:CREATE TABLE badge_h
On 11-Jul-01 Mike Baranski wrote:
> I was wondering if anyone had any suggestions on the following problem. I
> have a table with about 7 million rows, and I'm using the following
> join:CREATE TABLE badge_history_resolved SELECT badge_history.id AS id,
> badge_history.xact_date AS xact_date, ba
I was wondering if anyone had any suggestions on the following problem. I have a
table with about 7 million rows, and I'm using the following join:CREATE TABLE
badge_history_resolved SELECT badge_history.id AS id, badge_history.xact_date AS
xact_date, badge_history.xact_time AS xact_time, badg
11 matches
Mail list logo
