Message-ID: <gh-pgjdbc-pgjdbc-4077-c4515950669@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 22 May 2026 06:47:43 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #4077: pgjdbc: introduce @PgApi / @PgTags / @PgPropertyType annotations on PGProperty
In-Reply-To: <gh-pgjdbc-pgjdbc-4077@github.com>
References: <gh-pgjdbc-pgjdbc-4077@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 4515950669
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 4077
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/4077#issuecomment-4515950669
Content-Type: text/plain; charset=utf-8

Here's a use case for `status=HIDDEN`: https://github.com/pgjdbc/pgjdbc/pull/661/changes#diff-f1f17a9527eed81e0d547e9d6b7d5a00c62627e6c9ddeac6416fe290a2bd07d3L111-L112

We should not have removed enum entry `PGProperty.COMPATIBLE`, but we should rather deprecated it or made it hidden.