[GH-ISSUE #88] Add a way to update records based on non-primary unique column #63

New issue

Open

opened 2026-02-25 21:33:10 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 21:33:10 +03:00

Owner

Originally created by @Destroy666x on GitHub (Nov 7, 2018).
Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/88

As the title says. In some applications you don't mind primary keys changing and you have other fields that make the records unique. It would be nice to define the column that's supposed to be the identifier during diff generation.

Originally created by @Destroy666x on GitHub (Nov 7, 2018). Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/88 As the title says. In some applications you don't mind primary keys changing and you have other fields that make the records unique. It would be nice to define the column that's supposed to be the identifier during diff generation.

kerem commented

2026-02-25 21:33:10 +03:00

Author

Owner

@ilevennet commented on GitHub (Jul 18, 2019):

Yes, it's a good Idea. I have some problems with table with unique key.

@ilevennet commented on GitHub (Jul 18, 2019): Yes, it's a good Idea. I have some problems with table with unique key.

kerem commented

2026-02-25 21:33:10 +03:00

Author

Owner

@nkboscia commented on GitHub (Sep 9, 2021):

Yes, many tables do not have a primary key, so we can't use this tool. :( That should be stated in the prerequisites so people know before trying to use it.

@nkboscia commented on GitHub (Sep 9, 2021): Yes, many tables do not have a primary key, so we can't use this tool. :( That should be stated in the prerequisites so people know before trying to use it.