@parsonsmatt This should fix #299 by aggressively re-aliasing. Previously, if an already aliased value was discovered it would not be realiased. This caused an issue where an alias from a lower level could be mixed with an alias from a higher level. This only showed up as an issue when using set operations due to its "smarts" that try to avoid using more Idents than absolutely necessary.
As for version - there shouldn't be any changes to the behavior of the library, up to alpha equivalence on SQL queries. And it's a bug fix, not a new feature. I'd probably do a patch release.
@parsonsmatt This should fix #299 by aggressively re-aliasing. Previously, if an already aliased value was discovered it would not be realiased. This caused an issue where an alias from a lower level could be mixed with an alias from a higher level. This only showed up as an issue when using set operations due to its "smarts" that try to avoid using more Idents than absolutely necessary.
I guess this is a minor version bump?
I would like your eyes on this before I merge.