question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Date field values do not match with the ones shown by both, my system and mysql console

See original GitHub issue

System information:

  • OS: macOs High Sierra 10.13.6
  • DBeaver version: 6.1.10

Connection specification:

  • MySQL 8.0.16
  • JDBC
  • Not using tunnels or proxies

Describe the problem you’re observing:

The problem is kind of simple to describe. The past Monday I just downloaded the new release of your system, I installed it, and apparently, there wasn’t any problem. But right now I’m working with date fields, and I think that there could’ve been some trouble in your latest version. Basically, when try to store this information into the database:

Captura de pantalla 2019-06-12 a la(s) 12 06 53

Then, I dump this information in the browser to see what is being sent to the server:

Captura de pantalla 2019-06-12 a la(s) 12 09 45

And then, I store the record and the database shows incorrect values for the fields begining_date and expiration_date :

Captura de pantalla 2019-06-12 a la(s) 12 11 24

As you can see, the days in those fields seems to be decreasing by one, and a curious thing is that, today earlier, they were increasing.

But, the weirdest thing is that when I try to see the data in my system. It show this: Captura de pantalla 2019-06-12 a la(s) 12 13 09

And also when I do a query in Mysql CLI, it shows the same dates as the previous image.

Steps to reproduce, if exist:

Include any warning/errors/backtraces from the logs

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:15 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
ghostcommented, Aug 5, 2019

I just updated to the version 6.1.4 today (Aug 5th, 2019), but the error remains there for me too. What can we do? An error as basic like this and no one fixes it… I believe, no I’m sure, that many users are likely to be affected by this error and have not yet realized.

0reactions
kseniiaguzeevacommented, Aug 12, 2019

Verified

Read more comments on GitHub >

github_iconTop Results From Across the Web

B.3.4.2 Problems Using DATE Columns
If a date to be stored in a DATE column cannot be converted to any reasonable value, MySQL stores '0000-00-00' . To disallow...
Read more >
MySQL 5.7 Reference Manual :: 12.7 Date and Time Functions
DATEDIFF() returns expr1 − expr2 expressed as a value in days from one date to the other. expr1 and expr2 are date or...
Read more >
MySQL Tutorial :: 4.4.5 Date Calculations
MySQL provides several functions that you can use to perform calculations on dates, for example, to calculate ages or extract parts of dates....
Read more >
5.1.15 MySQL Server Time Zone Support
The session time zone setting does not affect values displayed by functions such as UTC_TIMESTAMP() or values in DATE , TIME , or...
Read more >
2 Server Error Message Reference - MySQL :: Developer Zone
Message: Column count doesn't match value count at row %ld ... Message: Can not modify more than one base table through a join...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found