Showing all 10 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
75615 | 2015-01-24 5:51 | 2018-05-15 23:44 | Connector / J | Analyzing (2144 days) | S2 | Any | Any | Incorrect implementation of Connection.setNetworkTimeout() | |
108993 | 2022-11-03 16:20 | 2022-11-04 4:02 | Connector / J | Analyzing (510 days) | S3 | Any | Any | fail to establish TLS connection when trust anchor exist in server's cert chain | |
109131 | 2022-11-17 22:04 | 2022-11-18 9:48 | Connector / J | Analyzing (496 days) | S3 | 8.0.31 | Any | Any | Wrong default clobCharacterEncoding |
109292 | 2022-12-06 9:28 | 2023-07-21 12:24 | Connector / J | Analyzing (251 days) | S2 | 8.0.19 and later | Any (Windows server) | Any | Retrieval of DateTime field with the value lost in DST lost hour causes error |
109929 | 2023-02-03 21:39 | 2023-03-16 4:54 | Connector / J | Analyzing (378 days) | S2 | Any | Any | after 8.0.23 upgrade, server time is not converting to JVM timezone | |
110242 | 2023-02-28 23:56 | 2024-01-22 9:15 | Connector / J | Analyzing (391 days) | S2 | 8.0.32 | Any | Any | zeroDateTimeBehavior=CONVERT_TO_NULL should apply to TIMSTAMP when date is zero |
110285 | 2023-03-06 21:33 | 2023-03-07 4:47 | Connector / J | Analyzing (387 days) | S2 | 8.0.32 | Any | Any | When using a CachedRowSet with a DATETIME field an exception is thrown |
112220 | 2023-08-30 10:27 | 2023-08-31 4:21 | Connector / J | Analyzing (210 days) | S3 | 8.0.33 | Any | Any | Create TimeStamp instance from DateTime in db for specific datetime |
112351 | 2023-09-15 2:17 | 2023-09-15 10:34 | Connector / J | Analyzing (195 days) | S2 | 8.0.30 | Any | Any | Incorrect implementation while locally creating Timestamp fields value in JVM |
112847 | 2023-10-26 18:45 | 2023-11-24 7:03 | Connector / J | Analyzing (153 days) | S5 | Any | Any | ResultSet.close for Large Tables with Slow Close Performance |
Showing all 10 (Edit, Save, CSV, Feed) |