We just upgraded our mysql from 5.0.32 on debian lenny, to 5.1.49 on
debian squish.
I wasn't told that it was doing an incremental version upgrade, i was
under the impression it was just going from 5.0.32 to 5.0.8x.
Anyways, I am getting some weird issues now, that is filling up the
syslog, and is looking for some insight on why???
Aug 4 10:07:17 --machine-- mysqld: 110804 10:07:17 [Warning] Statement
may not be safe to log in statement format. Statement: UPDATE
`freeradius`.`online_account` SET
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^I^I`update_time`=NOW()
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^I^I#, `type`='U'
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^I^I, `dup_ip`='N'
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^IWHERE `yearmonth`=
NAME_CONST('v_yearmonth',201108)
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^I^IAND `radacct_id`=
NAME_CONST('v_radacct_id',358954)
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^I^IAND `customer_id`=
NAME_CONST('v_customer_id',0)
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^I^IAND `customer_account_id`=
NAME_CONST('v_customer_account_id',0)
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^I^IAND `user_name`=
NAME_CONST('v_user_name',_latin1'usern...@domain.net' COLLATE
'latin1_swedish_ci')
Aug 4 10:07:17 --machine-- mysqld: ^I^I^I^I^IAND `framed_ip_address`=
NAME_CONST('v_framed_ip_address'
Aug 4 10:07:18 --machine-- mysqld: 110804 10:07:18 [Warning] Statement
may not be safe to log in statement format. Statement: UPDATE `user` SET
`last_refresh`=UNIX_TIMESTAMP() WHERE `user_id`='19' LIMIT 1
that is a direct pull from the syslog, i haven't changed anything
(except the machine name and the email address it was adding)
the first one, is called from a stored procedure, the second one, is
called from my php script.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
