-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Table Input Fails for MySQL datetime field #3759
Comments
Further analysis shows that timestamp values cause the same errors
... but not always. Retrieving data from a different MySQL Server works as expected (for datatime values at least) The reason is the option "supports timestamp data type" in the "Relational Database Connection" setting, which is rather unintuitive as it deals with timestamp and we're reading datetime values from the table. For me it is not clear what the option is for in the first place. Either MySQL/MariaDB supports these data types or not. And we're telling the "Relational Database Connection" which RDBMS we're connecting to. What would be the consequences of having this option selected and the RDBMS doesn't support timestamp? So would you please either set this option by default or at least provide a more speaking error message. Thank you very much. |
.take-issue |
Enabled the option by default on MySql and MariaDB as they support this. I also updated the error messages to include the description for the datatype as the integer value does not mean much to the end user. |
Apache Hop version?
2.8
Java version?
"11.0.22" 2024-01-16
Operating system
Linux
What happened?
Reading data from a MySQL/MariaDB table containing a datetime field fails with the following message for every row read:
In the result set all rows have values in that field.
Table Definition from database schema:
What's wrong?
Issue Priority
Priority: 1
Issue Component
Component: Database, Component: Hop Gui, Component: Hop Run
The text was updated successfully, but these errors were encountered: