List:General Discussion« Previous MessageNext Message »
From:Paul DuBois Date:February 23 2002 9:04pm
Subject:RE: Comments in Documentation
View as plain text  
At 19:54 +0200 2/23/02, savaidis wrote:
>I say "by default" means to do nothing, not to do the upercase conversion as
>I suppose it does to the fields.

As it happens, the standard SQL behavior for LIKE is to not be case
sensitive.  Which is roughly equivalent to doing an uppercase conversion.
You appear to be saying that it's a bad thing for MySQL to use the standard
behavior.

>I haven't met since now the "binary" as an alternative to "case sensitive"
>and I'm quite old in programming and age believe me :)
>Also if I knew SQL already, then I didn't have to read the MySQL manual.
>If you don't know there is a LIKE function then how to go and look for it?

Your original question appeared to imply that you already knew about LIKE,
and that you were wondering where it was in the manual.  Not that you were
wondering whether there was any such thing in SQL itself.

>
>Makis
>
>
>>  -----Original Message-----
>>  From: Paul DuBois [mailto:paul@stripped]
>>  Sent: Saturday, February 23, 2002 10:21 PM
>>  To: savaidis; mysql@stripped
>>  Subject: RE: Comments in Documentation
>>
>>
>>  At 19:28 +0200 2/23/02, savaidis wrote:
>>  >Instead of "binary" it sould be better to use a "case
>>  conversion" flag with
>>  >reverse function - NOT set by default.
>>
>>  You have to have *something* on by default.  I guess I don't
>>  understand
>>  what you're getting at.  I'd say BINARY is reasonably
>>  concise.  Perhaps
>>  you have an alternative, but you haven't actually specified
>>  any syntax,
>>  so it's difficult to say whether or not it might be better.
>>
>>  >   "Binary" doesn't make sence to me.
>>
>>  BINARY is nothing more than a synonym for "case sensitive".
>>
>>  >As for LIKE I think most WHERE commands use it so it is
>>  obvious it should be
>>  >there.
>>
>>  I disagree.  It is not obvious in the slightest that the
>>  section on WHERE
>>  should be turned into a list of possible functions that can
>>  be used there.
>>  Most such functions can also be used in the output column
>>  list, ORDER BY,
>>  GROUP BY, etc.  Functions should be documented in the section
>>  on functions.
>>  As, in fact, they are.
>>
>>  >
>>  >
>>  >Makis
>>  >
>>  >
>>  >>  -----Original Message-----
>>  >>  From: Paul DuBois [mailto:paul@stripped]
>>  >>  Sent: Saturday, February 23, 2002 6:29 PM
>>  >>  To: savaidis; mysql@stripped
>>  >>  Subject: RE: Comments in Documentation
>>  >>
>>  >>
>>  >>  At 16:01 +0200 2/23/02, savaidis wrote:
>>  >>  >Also there is not LIKE at all at SELECT command on MySQL manual!
>>  >>
>>  >>  http://www.mysql.com/doc/S/t/String_comparison_functions.html
>>  >>  http://www.mysql.com/doc/P/a/Pattern_matching.html
>>  >>
>>  >>  >I found manual very-very amateur work.
>>  >>  >I was trying about half hour to use  <WHERE FIELD1=
> "mpla-mpla%">
>>  >>
>>  >>  I'm surprised that if you wanted to use LIKE, that you didn't just
>>  >>  try it.
>>  >>
>>  >>  >Also "binary" at field creation or WHERE should be ON by default.
>>  >>
>>  >>  What would the syntax be for turning it off?
>>  >>
>>  >>  >  And WHERE
>>  >>  >works erroneously with Greek chars (without the "binary"
>>  >>  option). I think it
>>  >>  >is comfused by other languages chars so it should be an
>>  >>  option to declare
>>  >>  >the language character set at runtime (not at server cnf).
>>  >>  >
>  > >  > >Makis

Thread
mysql 3.23.49-1 rpm fails with redhat 7 thu 7.2simon23 Feb
  • Re: mysql 3.23.49-1 rpm fails with redhat 7 thu 7.2S. William Schulz23 Feb
    • Comments in DocumentationSteve Rapaport23 Feb
      • RE: Comments in Documentationsavaidis23 Feb
        • RE: Comments in DocumentationPaul DuBois23 Feb
          • RE: Comments in DocumentationTodd Williamsen23 Feb
          • RE: Comments in Documentationsavaidis23 Feb
            • RE: Comments in DocumentationPaul DuBois23 Feb
              • RE: Comments in Documentationsavaidis23 Feb
                • RE: Comments in DocumentationPaul DuBois23 Feb
                  • RE: Comments in Documentationsavaidis24 Feb
              • Doc Bug: Comments in DocumentationSteve Rapaport23 Feb
                • Re: Doc Bug: Comments in DocumentationArjen Lentz25 Feb
            • benchmarks?savaidis23 Feb
            • Re: Comments in DocumentationBob Hall24 Feb
          • extension to TUNING PRODUCTION MySQL SERVERvijay khanna24 Feb
        • Naming a Provider?D Nyberg23 Feb
          • RE: Naming a Provider?Venu23 Feb
    • Re: mysql 3.23.49-1 rpm fails with redhat 7 thu 7.2Doug Thompson23 Feb
  • Mysql dies with Signal 11Richard Clarke24 Feb
  • Re: mysql 3.23.49-1 rpm fails with redhat 7 thu 7.2(Trond Eivind Glomsrød)25 Feb
RE: mysql 3.23.49-1 rpm fails with redhat 7 thu 7.2Matthew Walker23 Feb
Re: Mysql dies with Signal 11Heikki Tuuri24 Feb
  • Re: Mysql dies with Signal 11Richard Clarke24 Feb
    • WEBppliance/PHPMyAdmin/MySQLGina24 Feb
Re: Mysql dies with Signal 11Sasha Pachev25 Feb