List:General Discussion« Previous MessageNext Message »
From:Scott Mackie Date:March 15 1999 4:08pm
Subject:Re: DISTINCT weirdness..
View as plain text  
I've had some problems with distinct before, in that if you have a query that
matches no values, you may have the number of rows reported being returned as 1.
This can be a pain to code around, but just more error checking really.
Scott Mackie
Virtual Service Inc.

Jay wrote:

> Can someone explain the internals of mySQL's "SELECT DISTINCT" ?
>
> I applaud TCX for it's informative online manual.. but this area seems a bit
> sparse.
>
> I've got a TEXT column I'm de-duping, so I brewed up a quick Perl/DBI
> de-duper..
>
> It only finds 1 dupe out of 3234 rows, where as SELECT DISTINCT .. into
> outfile 'foo' counts 2937 to the file.. so, 297 dupes. Right? (That is if a
> dupe is A = B)
>
> This is bizarre to me, I trust my script.. the single dupe it found is* 100%
> equal to another record.
>
> I spose I'll run it with... text_column like "$thingy" , and see what
> happens.
>
> Thanks..
>
> -Jay J
>
> ---------------------------------------------------------------------
> To request this thread, e-mail mysql-thread263@stripped
>
> To unsubscribe, e-mail the address in the List-Unsubscribe header.
> For additional commands, e-mail: mysql-help@stripped



Thread
DISTINCT weirdness..Jay15 Mar
  • Re: DISTINCT weirdness..Scott Mackie15 Mar
  • Re: DISTINCT weirdness..Martin Ramsch15 Mar
    • Re: DISTINCT weirdness..Michael Widenius15 Mar
      • Re: DISTINCT weirdness..Martin Ramsch17 Mar
  • Re: DISTINCT weirdness..Martin B. Jespersen16 Mar