unix-timestamp

As I spend most of my time with php and mysql or pgsql, I will use DateTime as a generic word for the date API. In php there is no "Date", "Time", "DateTime" and "DateTimeOffset" As I develop web application more and more elaborate, I use DateTime most of time, but sometimes I wonder if it is really what I want. for example it happens that I just want to display the today's date (for example when I want to store a forum or blog post), there is no calculation, no filter to provide, no iteration to happen... So why do I use \DateTime over the date() function? I saw this topic that provides some

I've been using the unix timestamp all my life. I like it because it's easy to compare, it's fast because I store it as an integer. And since I'm using PHP, I can get any date/time format with date() function from the unixtimestamp. Now, some people are saying that it's best to use the DATETIME format. But besides the more suited name, I don't see any advantages. Is it indeed better to use DATETIME, if so, what are the advantages? Thanks. If you store dates as Unix timestamps in the database, you're giving yourself the heavy lifting. You have to convert them to the formats you want to use, you

I have a blog where users can comment. I insert the time at which they posted a comment using NOW() and then use date('j M Y', stored timestamp) to show the time at which they posted. I want to know does NOW() return the locatime of the end user or the localtime at my server . Is it better suited to use UNIX_TIMESTAMP than NOW() to calculate the localtime at which users posted a comment. The function NOW() generates a formatted date-time string, determined by the time zone of your MySQL server. However, it would be better to store times using UNIX_TIMESTAMP() , which is expressed in GMT. Doing

I used "touch" on a file, updating the file's timestamp but the parent directory's timestamp did not change. However, (as expected) when I created a new file within the parent directory, the directory's timestamp did change. What criteria do UNIX-like operating systems (specifically AIX) use to determine when to update the timestamp of a directory? The timestamp is updated when the data that represents the directory changes. A change in a subdirectory of directory D does not change anything in the representation of D because D only points to the subdirectory, not to what's inside it. On the

I have the following entry in my DB table eventName(varchar 100) -> myEvent date(timestamp) -> 2013-03-26 09:00:00 and I am trying to use the following query; SELECT * FROM eventList WHERE `date` BETWEEN UNIX_TIMESTAMP(1364256001) AND UNIX_TIMESTAMP(1364342399) i.e between 2013-03-26 00:00:01 and 2013-03-26 23:59:59 but it is giving me 0 results. I have tried expanding the date range with no luck and there are definitely results within the range. any help is appreciated. Frank Conry Try: SELECT * FROM eventList WHERE `date` BETWEEN FROM_UNIXTIME(1364256001) AND FROM_UNIXTIME(1364342399) Or

How can I get an std::chrono::duration since a fixed date? I need this to convert a std::chrono::time_point to an unix timestamp. Insert code into XXX auto unix_epoch_start = XXX; auto time = std::chrono::system_clock::now(); auto delta = time - unix_epoc_start; auto timestamp = std::chrono::duration_cast<std::chrono::milliseconds>(delta).count(); I know time_point has a method time_since_epoch() but it's not guaranteed that this is the same as the unix epoch (00:00:00 UTC on 1 January 1970). bames53 A unix time stamp is defined as the number of seconds since January 1, 1970 UTC, except not