MySQL Community Server 5.6.27 Incorrect Datetime value: '1'

ChrisLeh

Grünschnabel
Hallo Forum,

ich habe ein seltsames Problem seit ich die Version 5.6.27 benutze.
Wenn ich ein TimeStamp Value in ein DateTime Colume einfügen möchte, bekomme ich immer die Fehlermeldung 1292. Incorrect datetime value '1'. Mir ist bewußt was diese Fehlermeldung bedeutet, nur finde ich absolute nicht den Fehler wo hier was incorrect ist.
SQL:
create table tmp_sa_rack_time(
`tmp_sa_rack_time_id` int(11) NOT NULL AUTO_INCREMENT,
`start_time` datetime,
`end_time` datetime
) ENGINE=InnoDB  DEFAULT CHARSET=utf8;
In diese Table möchte ich folgendes Eintragen
SQL:
insert into tmp_sa_rack_time
(start_time,end_time)
SELECT
  TIMESTAMP(in_out.start_time) AS start_time, TIMESTAMP(in_out.end_time) AS end_time
FROM
  in_out;
Das sind meine Ausgangswerte aus dem in_out (CREATE TEMPORARY TABLE in_out)
Code:
in_out.start_time | in_out.end_time
2016-01-18 16:56:12 2016-01-18 17:21:26
2016-01-19 10:51:05 2016-01-19 10:51:50
2016-01-19 11:05:01 2016-01-19 11:05:37
Ich habe es mit
SQL:
insert into tmp_sa_rack_time
(start_time,end_time)
SELECT
  str_to_date(in_out.start_time,'%Y-%m-%d %H:%i:%s') AS start_time, str_to_date(in_out.end_time,'%Y-%m-%d %H:%i:%s') AS end_time
FROM
  in_out;
und
SQL:
insert into tmp_sa_rack_time
(start_time,end_time)
SELECT
  cast(in_out.start_time as datetime) AS start_time, cast(in_out.start_time as datetime) AS end_time
FROM
  in_out;
versucht und bekomme immer die Fehlermeldung.
In meiner My.ini ist noch folgendes Eingestellt. Habe es schon mit und ohne Versucht.
Code:
explicit_defaults_for_timestamp=1

Danke für eure Hilfe ich bin für jeden Tip zuhaben.
 
Moin ChrisLeh,

kannst du es mal probieren mit
SQL:
INSERT INTO tmp_sa_rack_time
(start_time,end_time)
SELECT
  from_unixtime( unix_timestamp(TIMESTAMP(in_out.start_time))) AS start_time,
  from_unixtime( unix_timestamp(TIMESTAMP(in_out.end_time))) AS end_time
FROM
  in_out;

( wobei die innerste Casterei "TIMESTAMP(..)" sicherlich oversized ist.)

Alternativ ginge vermutlich auch:
SQL:
...
SELECT DATE_FORMAT(FROM_UNIXTIME(in_out.start_time),'%Y-%m-%d %H:%i:%s') as start_time
, ...

Grüße
Biber
 
Hallo Biber,
die 1. Version bringt ebenfalls die Fehlermeldung. Und bei der 2. Version ist der start_time Wert NULL und hier kommt auch die Fehlermeldung.

Grüße
Chris
 
Moin ChrisLeh,

hmm, und in der tempory table sind definitiv TIMESTAMPS drin?

Wenn ja, dann müssen wir beide jetzt auf die Profis warten.

Aber ich stehe auf jeden Fall zu meiner impliziten Aussage, dass beim Schreiben von TIMESTAMPs in DATETIME-Felder eine Konvertierung nötig ist.

Grüße
Biber

P.S.

Mein letzter Versuch wäre ein "...SELECT From_unixtime(deintimestamp) as deindatetimefeld".
Also ein paar Konvertierungen weniger.
 
Zuletzt bearbeitet:
Hallo Biber,
die tempory table ist in wirklichkeit ein Select was wie folgt aufgebaut ist. Ich wollte es nicht posten weil ich denke das hier nicht der Fehler liegt.
SQL:
  (SELECT
     if(@befor <= @start_time ,@befor:=@start_time,@befor:=0),
     timestamp(IF(@start_time <= sample_time.measure_time  AND @start_out=0 AND (sample_time.direction="OUT" AND sample_time.sensor = "T2") OR (sample_time.direction="IN" AND sample_time.sensor = "T3" ) , @start_time:=sample_time.measure_time,@start_time:=@befor)) as start_time,
     timestamp(IF(@end_time <= sample_time.measure_time AND @start_out=1 AND (sample_time.direction="IN" AND sample_time.sensor="T1") OR (sample_time.direction="OUT" AND sample_time.sensor="T3" AND sample_time.report_typ="PRO"),@end_time:=sample_time.measure_time,0))as end_time,
     timestamp(IF(@start_time <= sample_time.measure_time  AND (sample_time.direction="OUT" AND sample_time.sensor = "T2") OR (sample_time.direction="IN" AND sample_time.sensor = "T3" ) , @start_out:=1 ,0)) as start_time_in,  
     timestamp(IF(@end_time <= sample_time.measure_time AND @start_out=1 AND (sample_time.direction="IN" AND sample_time.sensor="T1") OR (sample_time.direction="OUT" AND sample_time.sensor="T3" AND sample_time.report_typ="PRO"),@start_out:=0,0))as end_time_out  
   FROM  
     (SELECT @start_time:=0, @end_time:=0,@befor:=0,@next:=0,@last_id:=0,@start_out:=0) as vars,
     (SELECT measure_time +0 as measure_time,direction,sensor,id_device, report_typ
     FROM tracking_history,tmp_sa_trackingtime as s_zeit
     WHERE
       ((find_in_set(tracking_history.id_device,s_zeit.path_id)
       AND report_typ!="PRO" )
       OR (id_sample=i_sample_id )) AND
       tracking_history.measure_time BETWEEN s_zeit.start_time AND s_zeit.end_time) as sample_time,
       (SELECT max(measure_time)+0 as i_endDate FROM tracking_history ) as max_time
   ) as in_out

hier werden die zwei Spalten als TimeStamp gewandelt und als start_time und end_time ausgegeben.

Ich hab noch was vergessen dieses SQL Beispiel läuft ohne Probleme auf einer DB Ver. 5.5.8
 
Zuletzt bearbeitet:
Hi BK,
ich habe folgendes zu meinem sql-mode hinzugefügt ALLOW_INVALID_DATES bekomme weiterhin die Fehlermeldung.
Ach ja ich habe dies als Informationsquelle genommen:
https://dev.mysql.com/doc/refman/5.6/en/sql-mode.html#sqlmode_allow_invalid_dates

Vielleicht ist ja was total falsch in meiner my.ini. Deswegen hier meine Einstellungen.
Code:
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]

port=3306

[ mysql]

default-character-set=utf8


# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[ mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3306


#Path to installation directory. All paths are usually resolved relative to this.
basedir="D:/MySQL/MySQL Server 5.6/"

#Path to the database root
datadir="D:/MySQL/Data/"

# The default character set that will be used when a new schema or table is
# created and no character set is defined
character-set-server=utf8

# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,ALLOW_INVALID_DATES"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
# table_cache=256

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=205M


# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before.  This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method.  This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=410M

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=354M

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K


#*** INNODB Specific options ***
innodb_data_home_dir="D:/MySQL/data/"

# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb

# Additional memory pool that is used by InnoDB to store metadata
# information.  If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS.  As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=15M

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=7M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system.  Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=1000M

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=343M

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=10

innodb_file_per_table
query_cache_type = 1
query_cache_min_res_unit = 4096
query_cache_limit = 1048576
max_sp_recursion_depth = 64

autocommit=0
# Set Slow Query Log
log-error=D:\MySQL\log\mysql_error.log
slow_query_log=1
slow_query_log_file=D:\MySQL\log\slow_query.log
general_log=1
general_log_file=D:\MySQL\log\general.log
# Binary Log
log_bin=mysql-bin
binlog_format = ROW
explicit_defaults_for_timestamp=0
 
Moin ChrisLeh,

zwei Sachen sind mir noch aufgefallen.
Erstens steht nun doch wieder in deiner .ini-Date als letzte Zeile "explicit_defaults_for_timestamp=0".

Zweitens deutet ja nun alles daruf hin, dass NULL-Werte in die tmp_sa_rack_time.start_time/end_time-Felder geschrieben werden sollen, wogegen irgendeine sinnvolle, aber offensichtlich gut versteckte Einstellung ihr Veto einlegt.

Kannst du nicht zumindest als Workaround diese NULL-Werte rausfiltern beim INSERT?
Also
SQL:
INSERT INTO
...
FROM
  in_out
WHERE in_out.start_time is not NULL and  in_out.end_time is not NULL;

Sonst geht es ja gar nicht vom Fleck...
Grüße
Biber
 
Hi Biber,
ich habe die Änderung gemacht, aber bekomme trotzdem die Fehlermeldung.
Select Anweisung
SQL:
insert into tmp_sa_rack_time
(start_time,end_time)
SELECT
  TIMESTAMP(in_out.start_time) AS start_time, TIMESTAMP(in_out.end_time) AS end_time
FROM
  (SELECT
  IF(@befor <= @start_time, @befor:=@start_time, @befor:=0),
  TIMESTAMP(IF(@start_time <= sample_time.measure_time
  AND @start_out = 0
  AND (sample_time.direction = 'OUT'
  AND sample_time.sensor = 'T2')
  OR (sample_time.direction = 'IN'
  AND sample_time.sensor = 'T3'), @start_time:=sample_time.measure_time, @start_time:=@befor)) AS start_time,
  TIMESTAMP(IF(@end_time <= sample_time.measure_time
  AND @start_out = 1
  AND (sample_time.direction = 'IN'
  AND sample_time.sensor = 'T1')
  OR (sample_time.direction = 'OUT'
  AND sample_time.sensor = 'T3'
  AND sample_time.report_typ = 'PRO'), @end_time:=sample_time.measure_time, 0)) AS end_time,
  TIMESTAMP(IF(@start_time <= sample_time.measure_time
  AND (sample_time.direction = 'OUT'
  AND sample_time.sensor = 'T2')
  OR (sample_time.direction = 'IN'
  AND sample_time.sensor = 'T3'), @start_out:=1, 0)) AS start_time_in,
  TIMESTAMP(IF(@end_time <= sample_time.measure_time
  AND @start_out = 1
  AND (sample_time.direction = 'IN'
  AND sample_time.sensor = 'T1')
  OR (sample_time.direction = 'OUT'
  AND sample_time.sensor = 'T3'
  AND sample_time.report_typ = 'PRO'), @start_out:=0, 0)) AS end_time_out
  FROM
  (SELECT
  @start_time:=0,
  @end_time:=0,
  @befor:=0,
  @next:=0,
  @last_id:=0,
  @start_out:=0
  ) AS vars, (SELECT
  measure_time + 0 AS measure_time,
  direction,
  sensor,
  id_device,
  report_typ
  FROM
  tracking_history, tmp_sa_trackingtime AS s_zeit
  WHERE
  ((FIND_IN_SET(tracking_history.id_device, s_zeit.path_id)
  AND report_typ != 'PRO')
  OR (id_sample = 27026))
  AND tracking_history.measure_time BETWEEN s_zeit.start_time AND s_zeit.end_time) AS sample_time, (SELECT
  MAX(measure_time) + 0 AS i_endDate
  FROM
  tracking_history) AS max_time) AS in_out
WHERE
  in_out.end_time is not null
and in_out.start_time is not null

Fehlermeldung
Code:
14:05:31   insert into tmp_sa_rack_time (start_time,end_time) SELECT  TIMESTAMP(in_out.start_time) AS start_time, TIMESTAMP(in_out.end_time) AS end_time FROM  (SELECT  IF(@befor <= @start_time, @befor:=@start_time, @befor:=0),  TIMESTAMP(IF(@start_time <= sample_time.measure_time  AND @start_out = 0  AND (sample_time.direction = 'OUT'  AND sample_time.sensor = 'T2')  OR (sample_time.direction = 'IN'  AND sample_time.sensor = 'T3'), @start_time:=sample_time.measure_time, @start_time:=@befor)) AS start_time,  TIMESTAMP(IF(@end_time <= sample_time.measure_time  AND @start_out = 1  AND (sample_time.direction = 'IN'  AND sample_time.sensor = 'T1')  OR (sample_time.direction = 'OUT'  AND sample_time.sensor = 'T3'  AND sample_time.report_typ = 'PRO'), @end_time:=sample_time.measure_time, 0)) AS end_time,  TIMESTAMP(IF(@start_time <= sample_time.measure_time  AND (sample_time.direction = 'OUT'  AND sample_time.sensor = 'T2')  OR (sample_time.direction = 'IN'  AND sample_time.sensor = 'T3'), @start_out:=1, 0)) AS start_time_in,  TIMESTAMP(IF(@end_time <= sample_time.measure_time  AND @start_out = 1  AND (sample_time.direction = 'IN'  AND sample_time.sensor = 'T1')  OR (sample_time.direction = 'OUT'  AND sample_time.sensor = 'T3'  AND sample_time.report_typ = 'PRO'), @start_out:=0, 0)) AS end_time_out  FROM  (SELECT  @start_time:=0,  @end_time:=0,  @befor:=0,  @next:=0,  @last_id:=0,  @start_out:=0  ) AS vars, (SELECT  measure_time + 0 AS measure_time,  direction,  sensor,  id_device,  report_typ  FROM  tracking_history, tmp_sa_trackingtime AS s_zeit  WHERE  ((FIND_IN_SET(tracking_history.id_device, s_zeit.path_id)  AND report_typ != 'PRO')  OR (id_sample = 27026))  AND tracking_history.measure_time BETWEEN s_zeit.start_time AND s_zeit.end_time) AS sample_time, (SELECT  MAX(measure_time) + 0 AS i_endDate  FROM  tracking_history) AS max_time) AS in_out WHERE  in_out.end_time is not null and in_out.start_time is not null   Error Code: 1292. Incorrect datetime value: '1'   0.031 sec
 
Hallo Alle,
danke für eure Bemühungen ich konnte das Problem nicht beheben und habe mir das ganze neu geschrieben und bin weg von den Datum werten.

Danke euch allen.
 
Zurück