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
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.
>> -----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!
>> >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