Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>tl;dr You should be fine as long as your <code>exec_time</code> column has a TIMESTAMP data type.</p> <p>There isn't an explicit UNIX_TIMESTAMP column datatype. There is a TIMESTAMP column data type. Values for columns of this data type are converted automatically from your client connection's time zone to UTC (a/k/a Z or Zulu time, f/k/a Greenwich Mean Time) when being converted from a date/time string and from UTC to your client connection's time zone upon conversion to a date/time string.</p> <p>So, if you're storing your <code>exec_time</code> column as a <code>TIMESTAMP</code>, you should be able to use the clause you propose:</p> <pre><code> WHERE exec_time &lt;= UNIX_TIMESTAMP() </code></pre> <p>This will work because both your <code>exec_time</code> values and the result of the <code>UNIX_TIMESTAMP()</code> function call are handled in UTC on the server side. Your <code>exec_time</code> values will be stored in UTC.</p> <p>If you're storing <code>exec_time</code> as an <code>UNSIGNED INT</code> or a similar numeric data type, you won't have been able to take advantage of the automatic conversion to UTC before storing.</p> <p>You can mess with the display conversion behavior by setting your client connection time_zone as follows:</p> <pre><code> SET time_zone='SYSTEM' /* for your system's local time */ </code></pre> <p>or </p> <pre><code> SET time_zone='+0:00' /* for UTC */ </code></pre> <p>or </p> <pre><code> SET time_zone'America/New_York' /* or 'Europe/Vienna' or whatever */ </code></pre> <p>Once you've issued one of these SET operations, do </p> <pre><code> SELECT exec_time, FROM_UNIXTIME(exec_time) </code></pre> <p>to get a sense of how your values are stored server side and translated.</p> <p>If you want to see what will happen eight days on, try this:</p> <pre><code> SELECT 3600*24*8+exec_time, FROM_UNIXTIME(3600*24*8+exec_time) </code></pre> <p><a href="http://dev.mysql.com/doc/refman/5.5/en//time-zone-support.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.5/en//time-zone-support.html</a></p>
    singulars
    1. This table or related slice is empty.
    1. POMySql UNIX_TIMESTAMP() stored as UTC with Daylight Savings approaching
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USO. Jones
    1. USO. Jones
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for this. I'm storing them as an unsigned int. As of tomorrow, times in GMT = times in UTC, so in theory the 4am example I gave should be ok? In PHP I am setting the timezone with date_default_timezone_set('Europe/Dublin'); and then using mktime($hour,$min,0,$month,$day,$year); to do the actual insert into the DB.
      singulars
      1. PO
      1. USNiall
    2. COGMT is a former name for UTC, the time of year notwithstanding. Do you mean British Time? You can check what will happen by setting your client time_zone='+0:00' then querying as I showed.
      singulars
      1. PO
      1. USO. Jones
    3. COSorry, yes I meant BST = UTC as of tomorrow. My clients are all (for now) using BST for their timezone. I'll try setting the client time zone now. Thanks
      singulars
      1. PO
      1. USNiall
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload