ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If you are using mysqli, then the mysqli_warning_count() function will tell you how many warning you have. You can then retrieve them using the SQL call SHOW WARNINGS. Check out the PHP manual for more details.
Distribution: Debian Wheezy/Jessie/Sid, Linux Mint DE
Not about the error message but about the error itself: 24:00 is not a valid time in MySQL. Although it should be, because it 2008-04-15 24:00 is the second after 2008-04-15 23:59.
After one full year developing a project which does a lot of date/time handling I found that it is generally better to do everything in Unix timestamps. That saves a lot of juggling between time/date and timestamps in PHP as well. Only for presentation one should use time/date, which is easy in PHP (gmtime and friends) and in MySQL any timestamp can be shown human readable as FROM_UNIXTIME(ts).
But that doesn't answer your original question, does it?
I expected the 24 to be the problem and running part of the query in the mysql client confirmed that. But it took me a while.
As I'm doing an update on an existing LAMP solution (that I wrote about 1.5 year ago) so it's a bit late to change the full design of my LAMP solution over to unix_timestamps. But I will definitely keep it in mind for the next application that I need to write.