Skip to content

Duplicate primary keys after type_2_scd_upsert (maybe) #85

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

Open
v01t6 opened this issue Feb 15, 2023 · 0 comments
Open

Duplicate primary keys after type_2_scd_upsert (maybe) #85

v01t6 opened this issue Feb 15, 2023 · 0 comments

Comments

@v01t6
Copy link

v01t6 commented Feb 15, 2023

Hello,

We came across a bug in your code (I think). You have to call the function type_2_scd_upsert with the same data, and you get incorrect behaviour (in my opinion). It is simple to induce. An example is shown below, where INVLDT_LVL_KEY is the primary key:

Original dataframe:
image

Updating dataframe:
image

After update (bug?):
image

Desired outcome?
image

We are using mack 0.2.0.

Thanks for your feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant