 |
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
SqlExplorer
Joined: 18 Sep 2011 Posts: 124 Country: United States |
|
tsv import predicting wrong source col size, can't change. |
|
Hi,
I'm trying to import a tab delimited file into both an existing table, and trying to generate the table on the fly.
2 problems:
1) There doesn't seem to be a way of changing the predicted source column size, before trying to import. So e.g., the MGRNAME column is being read as VARCHAR2(10), even though the maximum size in that file is 53. (The existing table is set at varchar2(255).
There doesn't seem to be any way of changing this, inside the import Step 2 of 3 window.
Also, I tried changing the column lengths in the project xml, and also had problems.
2) When I click the Analyze button, it says
can't convert variant of type (Error) into type (OleStr). I don't know what this means.
I was successful in setting up an import for a smaller tab delimited file.
|
|
Mon Apr 11, 2022 3:32 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
The "suggested type" column in the wizard is editable. You can click and edit them and enter correct type in case it can't automatically calculate data type correctly based on the data sampling analysis. .
|
|
Mon Apr 11, 2022 7:00 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
Sorry, I forgot to say, it's editable if you are importing data into a new table. Try entering a new non existing table name.
|
|
Mon Apr 11, 2022 7:06 pm |
|
 |
SqlExplorer
Joined: 18 Sep 2011 Posts: 124 Country: United States |
|
|
|
Thanks,
The Destination Column Type is Editable. But the Source Data type isn't Editable, and it's being calculated as smaller than it is.
|
|
Tue Apr 12, 2022 10:14 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
That source column is purely informational. It makes no real difference. Just be sure you choose a new table first time so you can change the types as you need. If you need to load another file, the it could go to the same table, column types will be retrieved from that table schema.
|
|
Tue Apr 12, 2022 10:56 am |
|
 |
SqlExplorer
Joined: 18 Sep 2011 Posts: 124 Country: United States |
|
|
|
Ok, I'm still having problems, but will try a few different scenarios.
btw, the analyze button doesn't work. I tried to save some time, because there are 67 fields in the table. But the analyze button returns an error that
Could not convert varient of type (Error) into type (OleStr).
I think there's a more recent build. I'll update that, first.
|
|
Tue Apr 12, 2022 11:58 am |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|