Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
\\...\\ .\\हिñçêČάй語简??한\\.xꏖ᠌ꁔꀥ: SQL operation is not supported.
at \\...\\ .\\हिñçêČάй語简??한\\.wꆠᢉ⣙ꈴ if 5.setAutoCommit(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.Wꂁꐵ7ᢊ.setAutoCommit(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.sꃁꆕꁵꊜ 7.process(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.sꃁꆕꁵꊜ 7.run(Unknown Source)
The exception is caused by the setAutoCommit call. Since MongoDB doesn't support transactions, I updated the Import code to skip the setAutoCommit call if a database doesn't support transactions.
While working on this issue, I realize that the Import Dialog needs some enhancements for MongoDB. Currently, if you have a newly created collection, the only field you can map in the Format tab of the Import Dialog is the "_id" field since this is the only field in the metadata. You cannot map other columns in the data file. Issue #8585 will make some enhancements to the Import Dialog for MongoDB.
Issue #8582 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 31817 |
| No time estimate |
The exception is caused by the setAutoCommit call. Since MongoDB doesn't support transactions, I updated the Import code to skip the setAutoCommit call if a database doesn't support transactions.
While working on this issue, I realize that the Import Dialog needs some enhancements for MongoDB. Currently, if you have a newly created collection, the only field you can map in the Format tab of the Import Dialog is the "_id" field since this is the only field in the metadata. You cannot map other columns in the data file. Issue #8585 will make some enhancements to the Import Dialog for MongoDB.