Message-ID: <gh-pgjdbc-pgjdbc-3396-c2584722934@github.com>
From: "crowmagnumb (@crowmagnumb)" <noreply+crowmagnumb@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 10 Jan 2025 23:08:16 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3396: SQLData Support
In-Reply-To: <gh-pgjdbc-pgjdbc-3396@github.com>
References: <gh-pgjdbc-pgjdbc-3396@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: crowmagnumb
X-GitHub-Comment-Id: 2584722934
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-01-10T23:59:28Z
X-GitHub-Issue: 3396
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3396#issuecomment-2584722934
Content-Type: text/plain; charset=utf-8

> Another way to support array, ( i made it In my own wrapper, and it works well ) . I just extended the SqlInput interface by adding new method to it:
> 
> ```
> readArray(Class<T> arrayElement)  
> ```
> 
> And in my SQLData i cast SQLInput to my SQLInputExt and just explicitly set element type. I make a map with simple types and compare them with java primitives and postgres primitives. And I take udt from connection.getTypeMap()

Ah, well I don't use readArray() either I use readObject(T[].class) and that works great. But I'm trying to support the full interface even if I won't use it.  :)