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
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | Tools - Import Tool |
| Version | 14.0 |
ADS version : ads-windows-x64-14.0-dev-44
Database:Sybase Anywhere 12/Sybase ASE15.7
Create following table
CREATE TABLE dbo.varvinary(
col1 varbinary(2) NULL
)
Now manually insert some data in this table,using the given below script and then import it to a text file or you can use the attached file for importing
INSERT INTO dbo.varvinary(col1)
VALUES(0xc1)
GO
INSERT INTO dbo.varvinary(col2)
VALUES(0xc2)
GO
INSERT INTO dbo.varvinary(col3)
VALUES(0xc3)
GO
Now go to Tools->Import Data->Connect to Sybase ASE 15.7->Import file(Use attached file),click next->From Schema and table drop down select respective values(varvinay table) and click next->In option tab from "Destination" drop down->choose "Import into database",click on next button->On Transaction tab set Transaction type:Batch,Batch size:1000,Threshold:0and wait time-1 and say next.This will throw error message over ADS window console.
If you follow the above given step and change option from "Import into database" to "preview INSERT statements" ,now copy generated script and insert it,record will get inserted.
|
18 B
|
|
77 KB
Please also check for "binary" data type.use the given below script.
CREATE TABLE dbo.binary1(
col binary(1) NULL)
I have Checked on ads-windows-x64-13.0-rc-4 and this issue does not occur on this build.
I have Checked on ads-windows-x64-13.0-rc-4 and this issue does not occur on this build.
Please also check for "timestamp" data type.use the given below table script.
create table time_ex(col1 timestamp)
GO
It works fine in ADS 13
Please also check for "timestamp" data type.use the given below table script.
create table time_ex(col1 timestamp)
GO
It works fine in ADS 13
This problem seems to have been introduced with our usage of prepared statements.
Prior to our prepared statement usage, one could insert data into varbinary if supplying hex input.
This problem seems to have been introduced with our usage of prepared statements.
Prior to our prepared statement usage, one could insert data into varbinary if supplying hex input.
Issue #8778 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
Please also check for "binary" data type.use the given below script.
CREATE TABLE dbo.binary1(
col binary(1) NULL)