At 9:45 -0600 3/8/03, Mark Matthews wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Description:
It is unbelievable that the MySQL ver 4.0 have so many bug, I
have been reported 2 bugs just a few days ago.
Now, I have found a bug again.
The bug is :
When I execute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Description:
It is unbelievable that the MySQL ver 4.0 have so many bug, I have been
reported 2 bugs just a few days ago.
Now, I have found a bug again.
The bug is :
When I execute "select * from old_topic where FID=4 and (
On Wed, Jul 04, 2001 at 07:16:50PM -0500, [EMAIL PROTECTED] wrote:
> Ok, I know I submitted an earlier bug report about this, but I've
> actually had it happen from the mysql monitor. Essentially, UPDATE
> queries are executing, but not actually updating, unless I SELECT
> data from the table fir
On 2001 Apr 13, Maciek Dobrzanski <[EMAIL PROTECTED]> wrote:
> > This is because with the first query it can use the index. With
> > the second query, it has to check the whole table. Why? Because
> > obviously you're using numbers. And let's make some_value == 10.
>
> I thought that maybe My
> This is because with the first query it can use the index. With
> the second query, it has to check the whole table. Why? Because
> obviously you're using numbers. And let's make some_value == 10.
I thought that maybe MySQL should check the field type and do the conversion
to string.
--
On 2001 Apr 13, Maciek Dobrzanski <[EMAIL PROTECTED]> wrote:
> | fd_10 | varchar(20) | | MUL | | |
> | fd_11 | varchar(20) | | | | |
>
> Now when I do this update:
> UPDATE test SET fd_11='value' WHERE fd_10='some_value'
> it usu
