Wrong datetime after Write in Database
Hi everyone,
I have process which retrieves data from a database, does some feature engineering and then store the result in another database.
One of the attributes is a datetime (CET timezone) and I would expect that the destination datetime is equivalent to the source. When I run the process locally, the process works as expected. When I run it on AI Hub (which I think is UTC or GMT), the output is a datetime shifted by 1 hour respect to the source one. Can you tell me how to setup correctly the connection so that it store the right results? I tried few options in the connection settings but no useful result.
Bests
I have process which retrieves data from a database, does some feature engineering and then store the result in another database.
One of the attributes is a datetime (CET timezone) and I would expect that the destination datetime is equivalent to the source. When I run the process locally, the process works as expected. When I run it on AI Hub (which I think is UTC or GMT), the output is a datetime shifted by 1 hour respect to the source one. Can you tell me how to setup correctly the connection so that it store the right results? I tried few options in the connection settings but no useful result.
Bests
Find more posts tagged with
Sort by:
1 - 1 of
11
If you don't, have you changed the connection settings discussed here (see accepted answer):
https://community.rapidminer.com/discussion/comment/68786
Best,
Michael