Updated 'column_definitions_sql' to ensure that only primary key key constraints are queried for

[BenMcH]

Fixes #850

Upon investigation into this query, I discovered that the new query is looking at the table sys.key_constraints which includes both primary keys as well as unique constraints, which is not what we want.

Originally, I tried adding this check to the where clause, but my schema dump was missing any table without a primary key. After adding this to the join, I was able to successfully dump my schema, build a test database, and run my specs successfully against the new test database.

CC @wpolicarpo

[wpolicarpo]

Looks good at first glance, but I'd like to double check with a minimal reproducible script before merging.

Do you think we could write a test for this?

[BenMcH]

I'll take a look at writing a test for this, yes!

[BenMcH]

@wpolicarpo All pushed up 😄

I reverted my change while writing the test, so I am sure that the test will fail if there is another regression. All tests were passing locally

[wpolicarpo]

Thanks for the contribution @BenMcH. I'll cut a new release soon.

[BenMcH]

Thank you @wpolicarpo! We look forward to pulling in the update 😄

[BenMcH]

@wpolicarpo is this going to be released soon?

[wpolicarpo]

Sorry for the delay here @BenMcH. I'll cut a new release today or tomorrow, I promise.

[wpolicarpo]

Version 6.0.1 released with your fix @BenMcH.

[BenMcH]

Thank you, @wpolicarpo!