MIME-Version: 1.0
References: 
 <CAMqTPqm7H4yVk0qGA8=TyTtVsNX88bo8x1BJkHc6vrOVYyW=RQ@mail.gmail.com>
 <CA+mi_8YNpi7a-OcWr3eWM4kRcCNPeapraSOif3yYCdTnxuuZwA@mail.gmail.com>
 <CAMqTPqmo=_Ev5R=0B93vgvxMf_RjiPkvJ_WqMEFbyK+Rx0MAsg@mail.gmail.com>
In-Reply-To: 
 <CAMqTPqmo=_Ev5R=0B93vgvxMf_RjiPkvJ_WqMEFbyK+Rx0MAsg@mail.gmail.com>
From: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: Wed, 11 Nov 2020 00:48:17 +0000
Message-ID: 
 <CA+mi_8ZL0W58C4d2-r9+mFEejWWdNJskp3s67usBD-ChShNiMQ@mail.gmail.com>
Subject: Re: Using composite types in psycopg3
To: Vladimir Ryabtsev <greatvovan@gmail.com>
Cc: psycopg@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, 11 Nov 2020 at 00:36, Vladimir Ryabtsev <greatvovan@gmail.com> wrote:
>
> Awesome, thanks.
>
> It would be great if it worked out of the box, as in other drivers.

I do agree.

I have much more experience with the text format, and in my
understanding not all the types support binary I/O. But my
understanding could be wrong.

After covering the binary format for the missing types (especially
numeric and date/time objects) we can probably do more testing and
check if defaulting to the binary format doesn't have unexpected
consequences.

Cheers!

-- Daniele