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 | Major |
| Complexity | Unknown |
| Component | Tools - Import Tool |
| Version | 15.0 |
Aqua Data Studio 15.0.0-dev-52
Build #: 35235
Built on: 2013-Dec-16 12:53:39 PM
Connect to postgresql
Create a schema named dbschema
Create two tables named "bit_string_datatype","textsearchdatatype" in dbschema
Create table script:
Fixed SELECT bit result set in query analyzer and fluid shell for Postgres. Fixed EXPORT bit output. Fixed IMPORT "Full" and "Batch" however batch will still not work as Postgres JDBC doesn't work correctly for the prepared statements. It doesn't handle bit arrays correctly. This is a known problem. If customer gets the following error using Batch suggest that they use Full as this piece works.
Import started ...
Execute batch failed: Batch entry 0 INSERT INTO "dbschema"."bit_string_datatype"("bit_col", "bit_col1", "varbit_col") VALUES('011', '1', '111') was aborted. Call getNextException to see the cause.
ERROR: column "bit_col" is of type bit but expression is of type character varying
Hint: You will need to rewrite or cast the expression.
Position: 91
Import completed.
1. Select now displays the correct value in the query analyzer, instead of True/False. Verified in 15.0.0-dev-91
2. Select now displays the correct value in the FluidShell, instead of True/False
3. Export now works correctly in 15.0.0-dev-91
4. Import - for Batch and Threshold, the message that tom attached is displayed to the user.
1. Select now displays the correct value in the query analyzer, instead of True/False. Verified in 15.0.0-dev-91
2. Select now displays the correct value in the FluidShell, instead of True/False
3. Export now works correctly in 15.0.0-dev-91
4. Import - for Batch and Threshold, the message that tom attached is displayed to the user.
Verified in ADS 15.0.0-dev-91
Verified in ADS 15.0.0-dev-91
@tom: This was woking before, but now in Dev-262 when I tested the Import in PostgreSQL 9.2 this doesn't seem to work. I get 2 exceptions - one the have.sql.BatchUpdateException together with
@tom: This was woking before, but now in Dev-262 when I tested the Import in PostgreSQL 9.2 this doesn't seem to work. I get 2 exceptions - one the have.sql.BatchUpdateException together with
Hi Tariq, Found a small bug that could affect export so I fixed that. Otherwise, all the tests seem to run OK. Would you give it a try? Thanks, Tom
Hi Tariq, Found a small bug that could affect export so I fixed that. Otherwise, all the tests seem to run OK. Would you give it a try? Thanks, Tom
Verified in dev-334.Works fine
Verified in dev-334.Works fine
Issue #11135 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 15.0.0-dev-329 |
| No time estimate |
2 issue links |
relates to #12003
Issue #12003Number Format Exception during Export in PostgreSQL |
relates to #11011
Issue #11011Wrong result displayed for bit datatype in PostgreSQL |
Fixed SELECT bit result set in query analyzer and fluid shell for Postgres. Fixed EXPORT bit output. Fixed IMPORT "Full" and "Batch" however batch will still not work as Postgres JDBC doesn't work correctly for the prepared statements. It doesn't handle bit arrays correctly. This is a known problem. If customer gets the following error using Batch suggest that they use Full as this piece works.
Import started ...
Execute batch failed: Batch entry 0 INSERT INTO "dbschema"."bit_string_datatype"("bit_col", "bit_col1", "varbit_col") VALUES('011', '1', '111') was aborted. Call getNextException to see the cause.
ERROR: column "bit_col" is of type bit but expression is of type character varying
Hint: You will need to rewrite or cast the expression.
Position: 91
Import completed.