From: Derek Downey
Date: September 9 2011 1:00pm
Subject: Re: strange mysql update ..
List-Archive: http://lists.mysql.com/mysql/225691
Message-Id: <B6D8FDA2-B9B7-4709-BB9A-17A88C93C59B@orange-pants.com>
MIME-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Try searching for a row that has a login_date of '0000-00-00 00:00:00'

- Derek

On Sep 9, 2011, at 8:52 AM, umapathi b wrote:

> Any update from anybody ?
>=20
>=20
> ---------- Forwarded message ----------
> From: umapathi b <umapathi.b@stripped>
> Date: Thu, Sep 8, 2011 at 4:28 AM
> Subject: Re: strange mysql update ..
> To: Ananda Kumar <anandkl@stripped>
> Cc: mysql@stripped
>=20
>=20
> Here is the o/p after the update ..
>=20
>=20
>           user_id: 16078845
>   drivers_license: TEST1140DL
>        login_date: 2011-06-19 11:20:07
>         course_id: 1011
>      regulator_id: 10840
>         test_info: 11111111
>   completion_date: 2011-06-19 11:37:16
>        print_date: NULL
>          password: test1140dl
> certificate_number: NULL
>             login: test1140dl@stripped
>=20
>=20
> - Umapathi
>=20
>=20
> On Thu, Sep 8, 2011 at 4:23 AM, Ananda Kumar <anandkl@stripped> =
wrote:
>=20
>> Can you lets us know what is the output of
>>=20
>> select * from user_info where user_id=3D16078845;
>>=20
>>=20
>> On Thu, Sep 8, 2011 at 1:02 PM, umapathi b <umapathi.b@stripped> =
wrote:
>>=20
>>> I wanted to change the login_date of one user . The original data of =
that
>>> user is like this ..
>>>=20
>>> select * from user_info where user_id =3D 16078845 \G
>>> *************************** 1. row ***************************
>>>          user_id: 16078845
>>>  drivers_license: TEST1140DL
>>>       login_date: 2011-06-19 11:20:07
>>>        course_id: 1011
>>>     regulator_id: 10840
>>>        test_info: 11111111
>>>  completion_date: 2011-06-19 11:37:16
>>>       print_date: NULL
>>>         password: test1140dl
>>> certificate_number: NULL
>>>            login: test1140dl@stripped
>>>=20
>>> I fired the update statement in a wrong way ..like this ..
>>>=20
>>> update user_info set login_date=3D'2011-08-05 04:15:05' and user_id
>>> =3D16078845
>>> limit 1 ;
>>> ( I forgot to use where . instead of where I used and )
>>> update user_info set login_date=3D'2011-08-05 04:15:05' where =
user_id
>>> =3D16078845 limit 1 ; ( this is the query intended )
>>>=20
>>> after the update ..I got this message ..
>>> mysql> update user_info set login_date=3D'2011-08-05 04:15:05' and =
user_id
>>> =3D16078845 limit 1;
>>> Query OK, 1 row affected, 1 warning (0.02 sec)
>>> Rows matched: 1  Changed: 1  Warnings: 0
>>>=20
>>> It shows that one record is affected and one row changed ..
>>> I did show warnings ..the output is like this ..
>>>=20
>>> mysql> show warnings;
>>>=20
>>> =
+---------+------+--------------------------------------------------------=
-+
>>> | Level   | Code | Message
>>> |
>>>=20
>>> =
+---------+------+--------------------------------------------------------=
-+
>>> | Warning | 1292 | Truncated incorrect DOUBLE value: '2011-08-05 =
04:15:05'
>>> |
>>>=20
>>>=20
>>> =
+---------+------+--------------------------------------------------------=
-+
>>>=20
>>> But I could not get any record in the table with the updated =
login_date ..
>>> mysql> select * from user_info where login_date like '2011-08-05%' ;
>>> Empty set (0.67 sec)
>>>=20
>>> So my question is what happened exactly ?
>>> Why no records updated ?
>>>=20
>>> Help is highly appreciated in this regard ..
>>>=20
>>> - Umapathi
>>> umapathi.b@stripped
>>>=20
>>=20
>>=20