Bug #73746 | ODBC Connector 5.3.4 MS Access #Deleted on Insert | ||
---|---|---|---|
Submitted: | 27 Aug 2014 17:38 | Modified: | 20 Jun 2016 7:32 |
Reporter: | Steven S | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51, 5.1.13, 5.2.7, 5.3.4, 5.3.6 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | #DELETED, MS Access, ODBC |
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
[15 Sep 2014 13:52]
Hemant Dangi
[15 Sep 2014 20:47]
Steven S
Error message you will see if you set NOT NULL in table
Attachment: Error.PNG (image/png, text), 6.23 KiB.
[16 Sep 2014 16:33]
Steven S
SQL Trace where a row is normally inserted, no null value issue
Attachment: SQLGood.LOG (application/octet-stream, text), 37.41 KiB.
[16 Sep 2014 16:34]
Steven S
SQL trace where the null #Deleted issue occurs
Attachment: SQLError.LOG (application/octet-stream, text), 16.66 KiB.
[18 Sep 2014 11:16]
Hemant Dangi
trace log for mssql
Attachment: sql_mssql.log (application/octet-stream, text), 52.60 KiB.
[18 Sep 2014 11:16]
Hemant Dangi
trace log for mysql
Attachment: sql_mysql.log (application/octet-stream, text), 40.43 KiB.