我遇到一个问题，我的 MySQL 表有一个存储 UTC 时间偏移的字段。该字段的类型为 TIME。这是出于遗留原因，我无法将列类型更改为更好的表示形式。然而 MySQL 支持这一点。它允许用户在时间字段中存储负值来表示负时间差。我使用 querydsl 生成实体类，并将该字段映射到 java.sql.Time 对象。现在，当数据库中有负值时，我面临一个问题。 java.sql.Time 类将任何负值转换为前一天的时间。例如，如果 DB 中的值为 -04:00:00，则 Java 对象的时间为 20:00:00。我正在考虑以某种方式将其转换为持续时间的选项，但后来遇到了 UTC 时区偏移在某些区域重叠的问题。
此处，负偏移量下降到 -12:00:00，正偏移量上升到 +14:00:00。现在的问题是我无法区分 Java 对象中 -12:00 和 +12 的值之间的差异，因为它们在 java 对象中都设置为 12:00:00。 +12:00:00 到 +14:00:00 两侧的值也有重叠。
任何处理这种情况的建议都将受到高度赞赏。
I ran into an issue where my MySQL Table has a field that stores a UTC Time Offset. The field is of the type TIME. This is for Legacy reasons and I cannot change the column type to a better representation. MySQL, however, supports this. It allows the user to store a negative value in a time field to represent a negative time difference. I use querydsl for the Entity class generation and it mapped this field to a java.sql.Time object. Now I am facing an issue when there is a negative value in the DB. The java.sql.Time class converts any negative value into the time in the previous day. For example, if the value in the DB is -04:00:00, the Java object has the time 20:00:00. I was considering an option of converting this somehow to a Duration but then I ran into the issue where UTC timezone offsets overlap in certain regions.
Here, the negative offset goes down to -12:00:00 and the positive side goes up to +14:00:00. Now the problem is that I can't tell the difference between the values in the Java object for -12:00 and +12 because they both set to 12:00:00 in the java object. +12:00:00 to +14:00:00 also has overlapping values from both sides.
Any suggestion to handle this situation is highly appreciated.
发布评论
评论（1）
我无法帮助 QueryDSL。
java.time
在java.time中，代表一个与 UTC 的偏移量 与
java.time.ZoneOffset类。您可以尝试这两种方法中的任何一种，看看它们是否有效。
将 MySQL
TIME文本解析为java.time.ZoneOffset也许你可以找回不幸的 MySQL
TIME值作为文本。然后解析为ZoneOffset对象。Retrieve as
ZoneOffset我不知道这是否有效，但您可以尝试直接将 MySQL
TIME提取为ZoneOffset。指定所需的 Java 类作为参数。I cannot help with QueryDSL.
java.time
In java.time, represent an offset-from-UTC with
java.time.ZoneOffsetclass.You might try either of these two approaches to see if they work.
Parse MySQL
TIMEtextually asjava.time.ZoneOffsetPerhaps you could retrieve your unfortunate MySQL
TIMEvalues as text. Then parse asZoneOffsetobjects.Retrieve as
ZoneOffsetI have no idea if this works, but you could try extracting the MySQL
TIMEas aZoneOffsetdirectly. Specify the desired Java class as an argument.