Bug #100747 AUTO_INCREMENT IDs fail in updatable prepared statements with useServerPrepStmt
| Submitted: | 4 Sep 2020 20:25 | Modified: | 5 Oct 2020 21:12 |
|---|---|---|---|
| Reporter: | Björn Voigt (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | Connector / J | Severity: | S3 (Non-critical) |
| Version: | 8.0.21 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | auto_increment, jdbc, prepared statement, ResultSet | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[4 Sep 2020 20:28]
Björn Voigt
[4 Sep 2020 21:02]
Björn Voigt
The stacktrace (within ' ' there is an unprintable character in original stacktrace)
Attachment: stacktrace1.log (text/x-log), 947 bytes.
[5 Oct 2020 21:14]
Björn Voigt
This demo shows the bug with Connector/J 8.0.21 and an Integer column
Attachment: ConnectorJBug100747B.java (text/x-java), 2.17 KiB.
[5 Oct 2020 21:17]
Björn Voigt
The stacktrace for example ConnectorJBug100747B.java
Attachment: stacktrace2.log (text/x-log), 891 bytes.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.