You might find that you'll get faster, better responses if you include at least some additional information. I mean, imagine how frustrated you would be if I replied "Well it works for me" and didn't give you any additional information or help!
But it does work for me; I just built a test case 10 minutes ago that works splendidly.
So let's dig a bit farther...
Please check the DB connect "Connection Health" page. Isolate your output that you are having problems with. Click around a bit in there - at some point you can get to the actual events that are showing the error. Include that here so we can help.
Also, perhaps it would be useful if you include the code you are using:
- The actual table you are sending to, if it differs from your example,
- The search you are using to send it there,
- The output of the search - or at least a row or two from it
- Any errors or warnings from the above dig-around in the DB Health pages.
For instance, I tried this:
In Mysql in a DB I already had set up as a connection in DBX, which I had write permission to:
CREATE TABLE answers_test (time_1 INT, time_2 DATETIME, field_1 VARCHAR(100));
I then created a DB Output in which I cobbled together a run-anywhere search to populate with one event of information.
| makeresults
| eval field_1 = "Something Random"
| eval time_1 = _time
| eval time_2 = strftime(_time, "%Y-%m-%d %H:%M:%S")
| fields - _time
This outputs (ignoring the poor formatting...)
field_1 time_1 time_2
Something Random 1561733073 2019-06-28 09:51:17
The rest of the steps in creating the output were
Picked answers_test from the list.
Mapped fields.
Scheduled it once every 100 seconds.
After that I jumped back to MySQL and ran:
mysql> select * from answers_test;
+------------+---------------------+------------------+
| time_1 | time_2 | field_1 |
+------------+---------------------+------------------+
| 1561733495 | 2019-06-28 14:51:35 | Something Random |
+------------+---------------------+------------------+
1 row in set (0.00 sec)
So you can see that not only was _time unformatted pushed into the INT field of time_1, time_2 also went in fine formatted like it is and as a DATETIME.
Please let us know if this helps!
... View more
