Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to insert data into Postgres db via SSIS #2656

Open
juliangordon opened this issue Sep 30, 2019 · 8 comments

Comments

@juliangordon
Copy link

commented Sep 30, 2019

Hi,

I am unable to insert data into a Postgres db using SSIS.

Error:
column "p1" does not exist

Steps to reproduce:

  1. Create table on target postgres db:
    CREATE TABLE public.test (
    "id" INT NOT NULL
    );

  2. Create dataflow task in SSIS to insert a row into above table. Source data is from another Postgres database. Can be any table containing integer values.

  3. Map dataflow from source to above destination table and execute SSIS package.

  4. Failure occurs on insert. Seems to be the way in which the npgsql connector generates the insert sql command for data to be inserted into the target database.

Regards,

Julian

Further technical details

Npgsql version: 4.0.10
PostgreSQL version: Aurora PostgresSQL
Operating system: Windows Server 2012

ETL Tool to move data:
SSIS

@juliangordon

This comment has been minimized.

Copy link
Author

commented Sep 30, 2019

ado destination mapping

@juliangordon

This comment has been minimized.

Copy link
Author

commented Sep 30, 2019

failure on insert

@austindrenski

This comment has been minimized.

Copy link
Member

commented Sep 30, 2019

@juliangordon Are there any logs showing the actual queries being sent?

@juliangordon

This comment has been minimized.

Copy link
Author

commented Sep 30, 2019

@austindrenski - Below is what the query looks like, when checking activity on the postgres db:

INSERT INTO public.test ("id") VALUES (p1)

@juliangordon

This comment has been minimized.

Copy link
Author

commented Oct 1, 2019

@austindrenski - I see that issue #2660 has been closed. Does this fix resolve the issue I am experiencing?

@austindrenski

This comment has been minimized.

Copy link
Member

commented Oct 1, 2019

@juliangordon Yes, that most likely fixes this too. Could you test the preview package for our next patch and report back?

@juliangordon

This comment has been minimized.

Copy link
Author

commented Oct 1, 2019

@austindrenski - Could you provide me with an msi of your latest preview please?

@roji

This comment has been minimized.

Copy link
Member

commented Oct 14, 2019

Just a thought: in the SQL above it seems like the parameter placeholder (@) is missing. ADO.NET drivers do expose some information on how to construct placeholders, we may have some sort of issue there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.