[SOLVED] Any PHP wizards here? I am trying to figure out if PHP's built in time() and mktime() functions can understand dates beyond 2038?
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Any PHP wizards here? I am trying to figure out if PHP's built in time() and mktime() functions can understand dates beyond 2038?
I've read some things that says on a 64bit machine and 64bit PHP it should be fine to go beyond the 32bit signed barrier, of which my VM meets both criteria (as far as I can tell) and yet my script just halts as soon as I try to get the unix_ts of a 2038 date.
mysql signed integers are +/- 2147483647 (January 19, 2038) but unsigned is 0 - 4294967295 (February 7, 2106)
Integers use 4 bytes of storage whereas bigint use 8 bytes of storage if anyone cares...
Instead of using any sort of "int," you should be using MySQL's provided date or datetime column types. Tell MySQL that the data being stored "is what it really is," and it will happily do the heavy lifting for you.
Instead of using any sort of "int," you should be using MySQL's provided date or datetime column types. Tell MySQL that the data being stored "is what it really is," and it will happily do the heavy lifting for you.
I know it's an option. I prefer unix timestamps though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.