ETL and Data Integration tools - Modern ETL software for everyone

Hello

We have been reviewing your product for purchase for a client and are happy with the FTP functionality and many other great features. The main database that will be used for this client is PostgreSQL 8.3.7 and we found that the Data Import wizard does not work with this database type; when we get to the stage of mapping the fields for import into the wizard after a long delay we receive the error: Cannot get list of fields for table test.public.xxxxxxxxxxxx Error SQLColAttribute Failed: HY092,ColAttribute for this type not implemented yet as shown in-line below. This was on a very simple table so I assume you do not support any PostgreSQL tables or field types in the import wizard at this point, is this true? We also did some testing with MS SQL so we know how it should work. Do you have plans on finishing the PosgreSQL functionality for this product?

We can use the PostgreSQL COPY command in an SQL script that runs under your products control on the server but this will require the import data to reside on the server or be directly accessible by the database server via the network. We were also hopping we could hand this off to the client and allow them to make simple changes using the Wizard. Do you have any other recommendations, can we provide the table field attributes to the wizard in some other fashion? What would you recommend?

Thanks for your time,
Ali

We are happy have a look at this problem and we will do our best to fix it.
But most likely it has something to do with he version of odbc diver you are using

So what is the version of odbc driver you got and can we ask you to email us table creation script please.

Why you are using ODBC anyway when you can use direct connections?

Mike

Mike,

Thanks for the very quick response.

Here is the table creation script, at first I thought it might be the record_id using the bigserial so I removed that field on a test copy of the table and received the same error:

-- Table: zjimgecmovement

-- DROP TABLE zjimgecmovement;

CREATE TABLE zjimgecmovement

(

gec_record_id bigserial NOT NULL,
gec_852_scan_date date,
gec_852_invoice_no character varying(8),
gec_852_store_no character varying(3),
gec_852_upc12 character varying(12),
gec_852_uom character varying(2),
gec_852_scan_qty bigint,
gec_852_activity_code character varying(2),
gec_852_price_id character varying(3),
gec_852_unit_price money,
CONSTRAINT zjimgecmovement_pkey PRIMARY KEY (gec_record_id)

)

WITH (OIDS=TRUE);
ALTER TABLE zjimgecmovement OWNER TO mfgadmin;
GRANT ALL ON TABLE zjimgecmovement TO mfgadmin;
GRANT ALL ON TABLE zjimgecmovement TO openmfg;
GRANT ALL ON TABLE zjimgecmovement TO jvalle;

We are using the PostgreSQL Unicode ODBC driver version 8.03.04.00, should we be using the ANSI version instead?

Ali

You need to tick parse statements as on picture below

Thank you,
Mike