Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not require typarray column when auto-registering extensions #632

Closed
wants to merge 1 commit into from

Conversation

chrischall
Copy link
Contributor

No description provided.

@mp911de mp911de added the type: bug A general bug label Feb 14, 2024
@@ -119,7 +119,7 @@ public Publisher<Void> register(PostgresqlConnection connection, ByteBufAllocato
}

private PostgresqlStatement createQuery(PostgresqlConnection connection) {
return connection.createStatement(String.format("SELECT oid, typname, typarray FROM pg_catalog.pg_type WHERE typname IN (%s)", getPlaceholders()));
return connection.createStatement(String.format("SELECT oid, typname, * FROM pg_catalog.pg_type WHERE typname IN (%s)", getPlaceholders()));
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Care to rewrite the SQL into SELECT * as that is a simpler variant?

@mp911de mp911de changed the title gh-631 - Do not require typarray column when auto-registering extensi… Do not require typarray column when auto-registering extensions Feb 15, 2024
@mp911de mp911de added this to the 1.0.4.RELEASE milestone Feb 15, 2024
@mp911de mp911de closed this in 24af094 Feb 15, 2024
mp911de added a commit that referenced this pull request Feb 15, 2024
@mp911de mp911de modified the milestones: 1.0.4.RELEASE, 1.0.5.RELEASE Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants