Which version of data-diff you have forked?

[Ryuk-me]

I believe you have forked an older version of data diff tool. Could you please tell me the reason for doing so?

Thank you.

[erezsh]

Hello @Ryuk-me ,

Do you mean why I didn't fork the most recent version?

I forked the last version that I know was stable. I then went manually through each commit that came after, and only applied it to reladiff if I thought it was good and necessary.

The commits that I didn't include are almost entirely either dbt-related, or are internal refactors. I also omitted the sqlserver implementation, because I don't think that it's correct.

But if there's anything important in data-diff that I missed adding to reladiff, I'm open to including it.

[grahamwetzler]

Just curious, why did you choose to not include the dbt stuff?

[erezsh]

Hi @grahamwetzler !

The dbt integration was a feature for reading the run config automatically from dbt, instead of having to specify it.

I removed the dbt integration because I thought it was a bad design. I might consider re-adding it as a separate command, e.g. reladiff-dbt. It would probably be best as an entirely separate tool that imports reladiff, since it doesn't need any special API or access to reladiff internals (iirc).

Either way, you can currently use Reladiff from dbt without any issue, either as a Python library or as a shell command.

[Ryuk-me]

Hey @erezsh thanks for replying.
I'll surely let you know if there is anything which needs to be included.
Great work !!