Skip to content

Bad Version Sorting #31

Closed
theory opened this Issue May 23, 2011 · 2 comments

1 participant

@theory
PostgreSQL Extension Network member
theory commented May 23, 2011

See pgmp. It shows 1.0.0 coming before 1.0.0b2, but it should be after 1.0.0b3. That is, it's not sorting as the highest number.

@theory theory was assigned May 23, 2011
@theory
PostgreSQL Extension Network member
theory commented May 24, 2011

Looks like this is because the old semver domain is deployed to production, rather than the new C type. And since the USING clauses were removed from the source, they no longer sort correctly.

So I'll have to schedule a downtime to switch to the C type.

@theory
PostgreSQL Extension Network member
theory commented Jun 2, 2011

Fixed yesterday by switching to the C semver type.

@theory theory closed this Jun 2, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.