Found the problem .. https://en.wikipedia.org/wiki/User_error Solution is: COLMAP ( usedefaults, TS_UPDATE = @DATE ( 'YYYY-MM-DD HH:MI:SS.FFF', 'YYYYMMDDHHMMSSFFF', TS_UPDATE ) ); (In all my edits/tests/re-runs, I erroneously edited wrong file .. O.o (but yes, all in initial dev testing, so all good ) )

Is there any way to extract more accuracy from updated? No. It is not possible to select the data which is absent in the table and cannot be calculated from the data present in the tables. does MySQL store more precision than the second, even though it shows only seconds? No. It stores exactly what you asked for. It can store up to microsecond - but you have not asked for this accuracy. Well, it really is déjà vu all over again with this question! There appears to be a bug in MySQL's implementation of this... (quelle suprise - a bug in MySQL...) at least on dbfiddle.uk and dbfiddle.com. – Vérace - get VACCINATED NOW You call NOW() - and you get the datetime without milliseconds. Call NOW(3) or NOW(6) and get more accurate value. https://dbfiddle.uk/?rdbms=mysql_5.7&fiddle=ccaf9b2c25e372c7bf0ca82c66ded787 Well, good news from the MySQL camp - you don't need to worry about fractional values of a second at all - 5.7 doesn't support them – Vérace - get VACCINATED NOW Never consult the person from the MySQL camp who said this nonsense again.

Store a time and the time zone name as text. Not timetz, which is broken and discouraged, and not just a time offset, which would break with daylight saving time (DST) and other time zone oddities. I suggest: CREATE TABLE reminder ( id int GENERATED ALWAYS AS IDENTITY PRIMARY KEY , user_id int NOT NULL REFERENCES "user"(id) ON DELETE CASCADE , scheduled_at time NOT NULL , tz text NOT NULL DEFAULT 'UTC' , created_at timestamptz NOT NULL DEFAULT now() ); To generate correct timestamps for "today" (as defined by your current TimeZone setting): SELECT * , (CURRENT_DATE + scheduled_at) AT TIME ZONE tz AS tstz , (CURRENT_DATE + scheduled_at) AT TIME ZONE tz AT TIME ZONE 'UTC' AS utc_ts FROM reminder; The resulting tstz may be on a different "day" for the receiver. utc_ts is the according timestamp in the UTC time zone. This related answer on SO fits precisely and has ample explanation: https://stackoverflow.com/a/13243029/939860 Aside: I wouldn't use the https://www.postgresql.org/docs/current/sql-keywords-appendix.html "user" as identifier.

And if you try it like that (syntaxis checking nowhere, alas):select extract(year from s.date) as year, extract(quarter from s.date) as quarter, extract(month from s.date) as month, s.xuids as xuids, s.titles as titles FROM ( select date, count(distinct xuid) as xuids, count(distinct titleid) as titles from sessions group by 1,2,3 ) AS s order by 1 desc,2 desc,3 desc; Presumption: First recalculations, then only work with dates, and only then sorting.

Let's assume that the variable is the current timestamp. Then the date document should be created like that.$array=array(); $array['date']=new MongoDate($time); $array['field']="value"; Then just use the conditions. $gt more than $lt less than that. To do this, you need to know the appropriate intervals, let's say the intervals are stored in timestamp in variables. $from and $toThen the necessary mass will have the following view.$condition=array('date'=>array('$gt'=>new MongoDate($from),'$lt'=>new MongoDate($to));

such things should be done in sql request. This should update all data over 15 seconds.UPDATE 'test_table' SET 'test_row' = 'test_text' WHERE 'id'= 1 and `time` < date_sub(now(), interval 15 SECOND) So, the idea is to update for the last 15 seconds only:UPDATE 'test_table' SET 'test_row' = 'test_text' WHERE 'id'= 1 and `time` BETWEEN timestamp(DATE_SUB(NOW(), INTERVAL 15 SECOND)) AND timestamp(NOW()) Otherwise, you're making one request for a sedition in the database, code calculations, and one request for an aptitude.In the right way, you're just sending the data to the base, and she's doing the drugs if you need to.

There's a special library to do that, I honestly don't remember what it's called to do with dates on the front. I think it's called a moment.Put it down and then you can do it like that:moment.unix(timestamp).format('DD.MM.YY HH:mm')

Range timestamp:$at = strtotime('25-04-2016'); //1461535200 $to = strtotime('26-04-2016'); //1461621600 SELECT * FROM table WHERE timestamp >= $at AND timestamp < $to Date range:SELECT * FROM table WHERE DATE(timestamp) = '2016-05-20' SELECT * FROM table WHERE timestamp >= '2016-05-20 00:00:00' AND timestamp <= '2016-05-20 23:59:59'

You use dog variables inside the procedure. They are intended for different purposes and retain their value as long as the link to the base is established. So they have to be initialized. Give special attention to the variables. StrToRead (parameter of your procedure) and @StrToRead - it's completely different variables that have nothing to do with each other!I don't see any need to do a procedure and a time table to accomplish your task. I suggest one request:select EventTime,RMS from ( select EventTime,RMS, @yes:=if(EventTime>@lt,1,0) YES, @lt:=if(@yes,EventTime+interval 10 second,@lt) from eventdata,(select @lt:='1970-01-01',@yes:=0) A where CHName='DSTN' and EventTime between '2016-04-14 21:00'+interval 10 second and '2016-04-14 21:00'+interval 10*(20+1) second order by EventTime ) A where YES=1 limit 20 Instead of the 2016 date, 10 and 20, you set variables with the necessary parameters - the starting date, the run-in interval, the number of records, respectively. Upper time limit will have to be removed if you have time-consuming data. I've put it on speed optimization, but if there's any data gaps, there's not enough lines.UPD: When approaching the procedure on your data, I'd like to isolate such an improvement (as is the case for such cases, the variables with dogs) :SET @startpoint:=TSbegin; REPEAT insert into temp_table_memory (TIME, RMS) SELECT @startpoint:=EventTime, RMS FROM backend_test.eventdata WHERE (CHName=DSTN) and (EventTime>@startpoint+INTERVAL dtsec SECOND) LIMIT 1; SET STR_to_read:=STR_to_read-1; UNTIL STR_to_read<=0 or FOUND_ROWS()<=0 END REPEAT; The trick is the variable with the @ Accepts the value during insert and shall not select max().

The simplest way:var valid = (new Date(timestamp)).getTime() > 0; var valid = (new Date('2012-08-09')).getTime() > 0; /// true var valid = (new Date('abc')).getTime() > 0; /// false UPDIt was a situation where JS didn't work MySQL TimeStamp.I found this decision:Date.mysqlTimeStamp = function(mysql_string){ var t, result = null; if( typeof mysql_string === 'string' ) { t = mysql_string.split(/[- :]/); result = new Date(t[0], t[1] - 1, t[2], t[3] || 0, t[4] || 0, t[5] || 0); } return result; }; Use this: timestamp = Date.mysqlTimeStamp(timestamp); UPD2Judging by https://developer.mozilla.org/ru/docs/Web/JavaScript/Reference/Global_Objects/Date , really, Javascript Not working. MySQL TimeStamp♪Function Date.mysqlTimeStamp shaves the line into the constituents so that the 4th approach from the documentation can be followed:new Date(year, month[, day[, hour[, minute[, second[, millisecond]]]]]); Consistency MySQL TimeStamp standardized, so a bold approach can be used Date.mysqlTimeStamp !

Here. https://stackoverflow.com/questions/6200972/hibernate-date-dont-save-the-milliseconds They say the problem is on Date itself. We need to use it. java.sql.Timestampjava.util.Date date = new java.util.Date(); java.sql.Timestamp timestamp = new java.sql.Timestamp(date.getTime());

Year, month, day and numberSELECT YEAR( FROM_UNIXTIME( user_time ) ) AS yer, MONTH( FROM_UNIXTIME( user_time ) ) AS MONTH , DAY( FROM_UNIXTIME( user_time ) ) AS DAY , COUNT( * ) AS cnt FROM user GROUP BY 1 , 2, 3 WITH ROLLUP He'll find out:Array ( [0] => Array ( [yer] => 2011 [month] => 5 [day] => 10 [cnt] => 20 ) [1] =&gt; Array ( [yer] =&gt; 2011 [month] =&gt; 6 [day] =&gt; 14 [cnt] =&gt; 8 ) [2] =&gt; Array ( [yer] =&gt; 2011 [month] =&gt; 7 [day] =&gt; 8 [cnt] =&gt; 22 ) [3] =&gt; Array ( [yer] =&gt; 2011 [month] =&gt; 8 [day] =&gt; 17 [cnt] =&gt; 10 ) /* Вырезано :))) */ [62] =&gt; Array ( [yer] =&gt; 2016 [month] =&gt; 2 [day] =&gt; 1 [cnt] =&gt; 59 ) [63] =&gt; Array ( [yer] =&gt; 2016 [month] =&gt; 3 [day] =&gt; 13 [cnt] =&gt; 44 ) [64] =&gt; Array ( [yer] =&gt; 2016 [month] =&gt; [day] =&gt; 13 [cnt] =&gt; 147 ) [65] =&gt; Array ( [yer] =&gt; [month] =&gt; [day] =&gt; 13 [cnt] =&gt; 4184 ) ) P.S. I asked myself, thank you. Keep kicking.

DATETIME stores a date-time in a local time belt. If you use a TIMESTAMP field, the value is stored in UTC and SELECT UNIX_TIMESTAMP(tsfield) I'll give you a full picture without a lap move. Alternatively, you can set a "sessional time belt" at the beginning of the session:SET @@session.time_zone='+00:00';

If there is a time zone, the standard solution is to keep Greenwich time. Any other decision will have to explain to everyone what time it is and why it's good.

Use it.print_r($service); echo "<br>"; $now = $service[1]['data']; // правильный индекс 1 $time = date("F Y", strToTime($now)); echo $time;

Update: replaced > ♪ >>in view of the additional requirement: add information fileand not rewrite it every time.For example:$ { curl example.com | tr -d '\n'; date +' %T'; } >> file tr -d '\n' remove the transfer of the line from extradition curl- Yeah.

If all columns in the first table are textual, then a function can be used to change the line at the date, for example https://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_str-to-date the second parameter indicating the appropriate https://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_date-format for sausage %d.%m.%Y %h:%i:%s It's quite appropriate for your case.I hope that the example will be clear: http://sqlfiddle.com/#!9/d8ee1/4 MySQL 5.6 Schema Setup:create table t1 (s varchar (100), d varchar (100), t varchar (100)); create table t2 (s varchar (100), d varchar (100), data date, vremja time, data_i_vremja datetime); insert into t1 values ("строка1", "ещё строка1", "27.06.2015 8:53:07"), ("строка2", "ещё строка2", "27.06.2015 11:48:57"); insert into t2 (s, d, data, vremja, data_i_vremja) select t1.s, t1.d, str_to_date (t1.t, "%d.%m.%Y %h:%i:%s"), str_to_date (t1.t, "%d.%m.%Y %h:%i:%s"), str_to_date (t1.t, "%d.%m.%Y %h:%i:%s") from t1; Query 1:select * from t1 http://sqlfiddle.com/#!9/d8ee1/4/0 :| s | d | t | |---------|-------------|---------------------| | строка1 | ещё строка1 | 27.06.2015 8:53:07 | | строка2 | ещё строка2 | 27.06.2015 11:48:57 | Query 2:select t1.s, t1.d, str_to_date (t1.t, "%d.%m.%Y %h:%i:%s") as data from t1 http://sqlfiddle.com/#!9/d8ee1/4/1 :| s | d | data | |---------|-------------|------------------------| | строка1 | ещё строка1 | June, 27 2015 08:53:07 | | строка2 | ещё строка2 | June, 27 2015 11:48:57 | Query 3:select * from t2 http://sqlfiddle.com/#!9/d8ee1/4/2 :| s | d | data | vremja | data_i_vremja | |---------|-------------|------------------------|---------------------------|------------------------| | строка1 | ещё строка1 | June, 27 2015 00:00:00 | January, 01 1970 08:53:07 | June, 27 2015 08:53:07 | | строка2 | ещё строка2 | June, 27 2015 00:00:00 | January, 01 1970 11:48:57 | June, 27 2015 11:48:57 |

You're making a mistake, right?moment.unix(timestamp); moment(timestamp*1000);

Two columns are selected in the SQL request, TaskDateDed And something else. SQL_CALC_FOUND_ROWS♪ TaskDateStart Just get out of there, apparently the object. $Task returning something to a non-existent attribution that php is a function data interprets as 0 (php likes to guess and think) and 0 in unixtime is 0:00 in the first January 1970 (epohi Yunix).Add the request. TaskDateStart♪ Somehow:$sql = "SELECT SQL_CALC_FOUND_ROWS ***, UNIX_TIMESTAMP(TaskDateDed) AS TaskDateDed**, UNIX_TIMESTAMP(TaskDateStart) AS TaskDateStart FROM task"; I just didn't realize the stars were symbolizing.

Didn't you try that?$time = strtotime('26/03/2014');