Re: bug in MySQL 5?

Octavian Rasnita wrote: From: "Gleb Paharenko" <[EMAIL PROTECTED]> Hello. In my opinion, it is not a bug. REPLACE has returned the sum of affected rows - one was deleted, and one was inserted. See: http://dev.mysql.com/doc/refman/5.1/en/replace.html Thank you. I have seen that's the true. I

Re: bug in MySQL 5?

From: "Gleb Paharenko" <[EMAIL PROTECTED]> > Hello. > > In my opinion, it is not a bug. REPLACE has returned the sum > of affected rows - one was deleted, and one was inserted. See: > http://dev.mysql.com/doc/refman/5.1/en/replace.html > > Thank you. I have seen that's the true. Is there any

Re: bug in MySQL 5?

Hello. In my opinion, it is not a bug. REPLACE has returned the sum of affected rows - one was deleted, and one was inserted. See: http://dev.mysql.com/doc/refman/5.1/en/replace.html Octavian Rasnita wrote: > Hi, > > I have tried: > > mysql> create table z(id int unsigned not n

Re: Bug in MySQL with Correlated Subqueries?

Are you saying this is a bug which has already been fixed for the next release? In any case, it may be worth noting that the manual says correlated subqueries "are inefficient and likely to be slow. Rewriting the query as a join might improve performance."

Re: Bug in MySQL with Correlated Subqueries?

At 13:59 27/3/2004, Ed Smith wrote: Hi, Below the results from a server built with BK 4.1 tree 3 days ago: C:\mysql\bin>mysqld --standalone --console --ansi --default-table-type=innodb 040328 0:36:59 InnoDB: Started; log sequence number 0 43634 mysqld: ready for connections. Version: '4.1.2-alpha

Re: BUG IN MYSQL

At 17:16 3/1/2004 -0700, Richard S. Huntrods wrote: Hi, I also checked this problem with my main database on a Solaris box (4.0.5a), and the problem did not occur. In this case the bug is a Windows MySQL server specific issue. I will upgrade to 4.0.17. Please do, it is the only solution for. --

Re: BUG IN MYSQL

On Sat, Jan 03, 2004 at 04:05:09PM -0700, Richard S. Huntrods wrote: I've submitted this problem three times now, and been ignored all three times. I guess bugs are simply not popular. Since the problem described below is 100% repeatable, I will now escallate it from "problem with delete/insert"

Re: BUG IN MYSQL

Udo, Thanks - I found the bug in the database. Looks like it's been fixed in 4.0.17 (the bug was reported in 4.0.14 and I'm running 4.0.15). The bug was also not in my Solairs system - using 4.0.5a. Thanks, -Richard Ugo Bellavance wrote: -Message d'origine- De : Richard S. Huntrod

Re: BUG IN MYSQL

Miguel, miguel solorzano wrote: At 16:05 3/1/2004 -0700, Richard S. Huntrods wrote: I've submitted this problem three times now, and been ignored all three times. Sorry for this inconvenience but I suggest you in the next time to use the MySQL's forums for to report bugs instead of the genera

Re: BUG IN MYSQL

I also ran the test, using MySQL 4.0.16, for apple-darwin6.6 (powerpc) on a Mac iBook G4 w/Panther and got no errors from mysqlcheck. You might try using mysqlbug to compose the bug report: http://www.mysql.com/doc/en/Bug_reports.html Hassan Schroeder wrote: Richard S. Huntrods wrote: I've

Re: BUG IN MYSQL

At 16:05 3/1/2004 -0700, Richard S. Huntrods wrote: I've submitted this problem three times now, and been ignored all three times. Sorry for this inconvenience but I suggest you in the next time to use the MySQL's forums for to report bugs instead of the general list:

Re: BUG IN MYSQL

Richard S. Huntrods wrote: I've submitted this problem three times now, and been ignored all three times. I guess bugs are simply not popular. Since the problem described below is 100% repeatable, Uh, well, maybe not quite :-) I've distilled the problem I'm having with DELETE/INSERT to an even

RE: BUG IN MYSQL

> -Message d'origine- > De : Richard S. Huntrods [mailto:[EMAIL PROTECTED] > Envoyé : Saturday, January 03, 2004 6:05 PM > À : [EMAIL PROTECTED] > Objet : BUG IN MYSQL > > > I've submitted this problem three times now, and been ignored > all three > times. http://bugs.mysql.com/ >

Re: Bug in MYSQL replication

On 31 Mar 2003 at 16:39, Dyego Souza do Carmo wrote: > this is a bug... because i modify the database escribaupdate from > database mysql and this is not logged... Yes, it is a bug, but you can work around it by using replicate-wild- do-table. See the documentation for the replicate-do-db option

Re: Bug in MYSQL replication

You may consider it a bug, but it is the documented behavior. Dyego Souza do Carmo wrote: I'm using MySQL/InnoDB 4.0.12 I set replication to replicate only database escribaupdate... The bug is: I connect in database escribaupdate and run: delete from escriba_autorizacao; go to shell and execut

Re: Bug in MySQL privilege system?

Harald Fuchs writes: > [This is for MySQL 4.0.1 alpha on Linux 2.2.18-SMP, if it should matter] > > Either I misunderstand the manual, or I found a small bug. Consider > the following command sequence: > > mysql -e 'CREATE DATABASE t1' > mysql t1 -e 'CREATE TABLE t1 (id INT)' > mysql -e 'G

Re: Bug in MySQL API ?!?

Hi! I have a couple of small comments to Sinisa answer. > "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes: Sinisa> Skriniar Gregor writes: >> Dear all, >> >> I experienced some problems with using MySQL API: >> My problem is that if I don't use database a long time it is disconn

Re: Bug in MySQL API ?!?

Hi! I have a couple of small comments to Sinisa answer. > "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes: Sinisa> Skriniar Gregor writes: >> Dear all, >> >> I experienced some problems with using MySQL API: >> My problem is that if I don't use database a long time it is disconn

Re: Bug in MySQL API ?!?

At 15:45 +0100 2/4/02, Skriniar Gregor wrote: >Dear all, > >I experienced some problems with using MySQL API: >My problem is that if I don't use database a long time it is disconnected and That's how it's supposed to behave. What's the bug? If your application really needs to hold the connectio

Re: Bug in MySQL API ?!?

Skriniar Gregor writes: > Dear all, > > I experienced some problems with using MySQL API: > My problem is that if I don't use database a long time it is disconnected and when I >try to connect again at first I use method mysql_ping(), which reopens connection and >that's the point. Please see n

Re: Bug in MySQL-4.0

Fournier Jocelyn [Presence-PC] writes: > Hi, > > I caught a bug in MySQL-4.0, but I don't know how to reproduce it ;) > > Here is the description : > > mysqld got signal 11; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked agais

Re: Bug in Mysql access rights ?

BAUMEISTER Alexandre writes: > Bonjour, > > What's happening ? > > Regards, > Alex. Your story is quite strange. Can you run SHOW GRANTS on both user@localhost and user@remoteIP and see what they are showing ?? -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr

Re: Bug in Mysql C API?

Rafael Martinez writes: > Hei > > If I send a SELECT sql-request to my DB and this request returns an > "Empty set" ... > > mysql_num_rows(MYSQL_RES *result) returns 0 - This is OK > but mysql_num_fields(MYSQL_RES *result) returns 1 - This is not OK ;-) > > Why? Am I missing anyth

Re: Bug in MySQL 3.22 ?

I would say that's because mysql thinks that "-" is subtraction and not a hyphenation. You could try: mysql> drop database 'planhouse-broke'; or delete the directory called 'planhouse-broke'. and in future, I think you'll save yourself a lot of agro if you use underscore instead. O | O \

Re: Bug in MySQL TRIM() Function! ?

Hi! > "Matt" == Matt Wagner <[EMAIL PROTECTED]> writes: Matt> Paul Wisén writes: >> This works: >> mysql> select trim('foo' FROM 'foobaar'); >> ++ >> | trim('foo' FROM 'foobaar') | >> ++ >> | baar | >> +-

Re: Bug in MySQL TRIM() Function! ?

I think it would have to be considered a simple bug. If you're not convinced by the 'both' example he gave, here's one that's even more obviously a bug: mysql> select trim(leading 'foo' from 'foo'); ++ | trim(leading 'foo' from 'foo') |

Re: Bug in MySQL TRIM() Function! ? / Set element solution

I guess I can replace it with a null string.. select REPLACE('foo', 'foo', ''); Works just fine! Thanx! Well, then my SET problems is fixed. I wanted a way to add, replace or remove elements in a set without doing it with any extra code. fyi then, this could come handy. To: Add an element

Re: Bug in MySQL TRIM() Function! ?

Hi, >> This works: >> >> mysql> select trim('foo' FROM 'foobaar'); >> ++ >> | trim('foo' FROM 'foobaar') | >> ++ >> | baar | >> ++ >> 1 row in set (0.00 sec) >> >> This does not work: ! >>

Re: Bug in MySQL TRIM() Function! ?

Paul Wisén writes: > This works: > > mysql> select trim('foo' FROM 'foobaar'); > ++ > | trim('foo' FROM 'foobaar') | > ++ > | baar | > ++ > 1 row in