I am comparing two versions of a vendor application db, and sometimes they change columns names (even when not necessary). The tool needs a way to bind these two together.

It could be done with a simple mechanism under the hood, like simply creating a (new) common field alias name between the two queries.

It would be good if it could be implemented to allow general sql field query/conversion logic (where meaningful). For instance, sometimes even when keeping the name identical, other aspects of the field might have been changed which could lead to false positives for changes.

e.g. a number now encoded with greater precision, though the value is only different by zeros padded at the end. Or a date encoded to a string in a different format, now. (don't ask why, it just happens). If we could apply the available conversion logic from the underlying DBMS when creating this alias, that could take care of a lot of this stuff.