On 02/10/2012 01:24 PM, Reindl Harald wrote:
> so this is really a showstopper because there are many people which
> would kill me if i break autoreplies with a update, so currently
> i can update the "small server" tomorrow night because there are
> no replies and no backend communicated to users
I've done a small update where we now use NOW() instead of
CURRENT_TIMESTAMP
The CURRENT_TIMESTAMP was causing problems with preparedstatements in
PostgreSQL, so maybe something similar is going on in MySQL.
You could increase the logging on MySQL and check the error log.
Another small change that came along with this one: start_date and
stop_date now must be specified. Or rather, they were already required
but the query suggested they could be NULL which they couldn't.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/i...@nfg.nl/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
