Open ibbenz opened 2 years ago
Hi @ibbenz I tried to reproduce your error - and I'm not sure if I was successfull. I opened your SIARD archive using the latest realese (2.2.11, see https://github.com/sfa-siard/SiardGui/releases/tag/2.2.11 and used it to convert your archive to the latest SIARD 2.2 Format.
hint: editing any field and saving the archive will convert it to SIARD 2.2.
And then tried to upload the archive to the oracle db - I've got a similar, but slightly different error:
I think that is a slightly different error - could you check what error you got and maybe convert use the latest release?
The errors are the same. The error to which I referred in my issue was the one at the bottom of your window: "Archive upload failed .....: value too large for column .... bitnTest (actual 2, maximum: 1)
With regard to the difficulties with dates in general I have already set up an issue more than a month ago.
A different but bit(N) related error occurs, when I try to load the data into Microsoft SQL instead of Oracle:
String or binary data would be truncated in table 'SQLTestSuite.SimpleDB.Employees', column 'bitnTest'. Truncated value: ''.)!
I have a .siard 1.0-file with BIT VARYING(2) data. When uploading the .siard file to an ORACLE database the following error message appears:
(actual: 2, maximum: 1))! Partial upload may have to be deleted manually.
Similar errors occur with other numbers n for BIT VARYING(n): actual: n, maximum 1
You can use the attached file in order to reproduce the error: The BIT VARYING data is in the last column of table6 of the .zip file 0_1-3_Northwind_simple_220913_Siard_V02.zip