Message-ID: <gh-pgjdbc-pgjdbc-3926-c4028239121@github.com>
From: "dkozlov-de (@dkozlov-de)" <noreply+dkozlov-de@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 10 Mar 2026 02:49:06 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3926: ResultSetMetaData.getColumnClassName is broken for jsonb
In-Reply-To: <gh-pgjdbc-pgjdbc-3926@github.com>
References: <gh-pgjdbc-pgjdbc-3926@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: dkozlov-de
X-GitHub-Comment-Id: 4028239121
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2026-03-10T15:21:18Z
X-GitHub-Issue: 3926
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3926#issuecomment-4028239121
Content-Type: text/plain; charset=utf-8

I vote for the fix to this problem. This is clearly a bug. Metadata must return correct class data, otherwise, it is absolutely useless. This issue breaks any libraries that provide dynamic data type resolution based on the column metadata. At some point jsonb started being treated as a String. Well, that was a developers' call (even though it is still not clear to me what the reason for that change was). But if that (changing PGobject to String) was done in metadata, retrieving the column data would have to be changed accordingly to return a String instead of PGobject.