Re: possible bug?

Dont know if its an automatic answer or what but.
If i cant get my report to somebody the possible bug wont be fixed.
If it wont be fixed i wont be use mysql.
thats all.



On Wed, 17 Jul 2002 bugs@lists.mysql.com wrote:

> Date: Wed, 17 Jul 2002 10:13:41 +0200
> From: bugs@lists.mysql.com
> To: KISS Akos
> Subject: Re: possible bug?
>
> Your message cannot be posted to bugs@lists.mysql.com because it did not
> follow the format expected by our spam/off-topic filter. To this list we
> accept only repeatable bugs reports, meaning that you can describe a
> set of steps we can follow to repeat the bug on our systems.
>
> If you are having problems with MySQL but are unable to provide the required
> description, and have not purchased a support contract from MySQL AB,
> you should send your message to mysql@lists.mysql.com and possibly one of our
> knowledgable users or developers will help you. However, we do not guarantee
> that every message on mysql@lists.mysql.com will be answered. We can afford
> to provide free code, but unfortunately, we cannot afford to provide
> guaranteed free support on top of that. We do, nevertheless, fix our bugs
> regardless of who reports them and whose systems they affect, and will
> investigate your problem if you can prove to us with a test case that the
> error is in our code and not yours.
>
> If you have purchased a support contract from MySQL AB, you should follow
> the standard support request procedure to report this problem. Support
> contracts are available at https://order.mysql.com/.
>
> If you are able to describe how we can repeat the problem, include the string
> "How-To-Repeat:" in the body of your message, followed by the detailed
> description of what we need to do to make it happen, and our filter will
> accept your message. If you use mysqlbug script, which comes with the MySQL
> distribution, to post the message, it will be automatically accepted.
>
> You have written the following:
>
> ---start of your message----
> server version: 3.23.49-log
>
> found a bug, dont know if fixed.
>
> mysql> SELECT '\\asdasd {' RLIKE CONCAT(CHAR(92),'.\+{');
> +--------------------------------------------+
> | '\\asdasd {' RLIKE CONCAT(CHAR(92),'.\+{') |
> +--------------------------------------------+
> | 0 |
> +--------------------------------------------+
>
> temp solution:
>
> SELECT bla FROM ehh WHERE bla!=REPLACE(bla,'\\\{','\{');
>
>

--
KISS Akos
kaz@telemedia.hu


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12198@lists.mysql.com
To unsubscribe, e-mail

Re: possible bug?

Hi.

On Wed 2002-07-17 at 10:34:37 +0200, kaz@telemedia.hu wrote:
> Dont know if its an automatic answer or what but.
> If i cant get my report to somebody the possible bug wont be fixed.
> If it wont be fixed i wont be use mysql.
> thats all.

Would you have followed the bug reporting procedure described in
several places, including the manual, the tool mysqlbug would not only
have provided more information, but also the little required phrase
"how-to-repeat", which would have made your report pass without trouble.

Effectively you are complaining about your absense of following the
bug reporting guidelines.

[...]
> > server version: 3.23.49-log
> >
> > found a bug, dont know if fixed.
> >
> > mysql> SELECT '\\asdasd {' RLIKE CONCAT(CHAR(92),'.\+{');
> > +--------------------------------------------+
> > | '\\asdasd {' RLIKE CONCAT(CHAR(92),'.\+{') |
> > +--------------------------------------------+
> > | 0 |
> > +--------------------------------------------+

This is expected behaviour.

Backslash "\" resp. CHAR(92) is a special character within regular
expressions and therefore has to be escaped. Therefore it must be

SELECT '\\asdasd {' RLIKE CONCAT(CHAR(92),CHAR(92),'.\+{')

or shorter (with double backslash, as one level of escapes is "eaten"
by the mysql client)

SELECT '\\asdasd {' RLIKE '\\\\.\+{'

And since "{" has a special meaning, too, it should be escaped, too,
although in the above context the parser can see that it is not used
in its special meaning. While "\+" is an escape, that only the client
will see, and since "+" has no special meaning to the client, but in
the regexp, "+" is enough. Therefore the select should be

SELECT '\\asdasd {' RLIKE '\\\\.+\\{'

which will be parsed by the mysql client and to the server it will
send effectively

SELECT '\asdasd {' RLIKE '\\.\{'

which shows why a double CHAR(92) is needed if the backslashes are
replaced by this.

Regards,

Benjamin.

--
benjamin-mysql@pflugmann.de

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12203@lists.mysql.com
To unsubscribe, e-mail

Re: possible bug?

> SELECT '\\asdasd {' RLIKE '\\\\.+\\{'

oh, sorry, youre right i mistyped the regex. thanks for the ANSWER.

--
KISS Akos
kaz@telemedia.hu


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12204@lists.mysql.com
To unsubscribe, e-mail