Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlNdw-002WGQ-TX for pgsql-jdbc@arkaria.postgresql.org; Wed, 27 Sep 2023 06:03:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qlNdv-000hdq-IA for pgsql-jdbc@arkaria.postgresql.org; Wed, 27 Sep 2023 06:03:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlNdv-000hdV-A1 for pgsql-jdbc@lists.postgresql.org; Wed, 27 Sep 2023 06:03:27 +0000 Received: from mail-ua1-x92e.google.com ([2607:f8b0:4864:20::92e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qlNds-006sGn-1Y for pgsql-jdbc@postgresql.org; Wed, 27 Sep 2023 06:03:26 +0000 Received: by mail-ua1-x92e.google.com with SMTP id a1e0cc1a2514c-7abbe1067d1so2539349241.0 for ; Tue, 26 Sep 2023 23:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695794603; x=1696399403; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=UR0E5xi5lv7kjQfSVSYw7C9a4mlf/oYnCuy5U8juLJA=; b=Iy/U9M3xqSw9MVGJaBSGxfY92PePGAfx2UMLBsn5u70A8m5UpG7pT9zcT95VvOJ9mK n7Rva6L7k7GE3qo5EnBbLUu4YuPE2kQ5w78SKflynUcvOd6ObGcwir/DQRs/sUcRcZuY efQ6PDnIDKKFi0hQj2YB4QXMfPZuLLtKiEVq74i6bJRz6wDfkvuVvb/ktVuNespdCSNd Yxiv/ksnXTlGf6v5uMtCYviNVq4tK3y6UEF4VlhyGyJiN6kWwZjExjYtiumaFc0i9c9b sOPYL27uq0W81HGM7i8yb6NiC+9QxYREig5ixeCKkdaTK5Ir34/faGywXfS4KDJ5E8nP thiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695794603; x=1696399403; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=UR0E5xi5lv7kjQfSVSYw7C9a4mlf/oYnCuy5U8juLJA=; b=oZ7UPA0Z6naNHOrrX+6ApI61Xe+yaVAtizZ6u60albCD0FJ5xeTjkqEDcBffkTqppX 8K4hyBXvFISGPrj1ktXjr2Czkj4fk6SbbMO/SMjdJIexHbpVH6nuv8wbxuPsyYsJCUJ3 GCsLdS+idft1DA9SGhuUyVDkrZ5mUb6YYNUgjCVsXe6p3socb4EisOR+sf6MECH/25l3 iZYJ2q1EUuEp+BTMOwIEdYgfu2JPMa4TfRDj3hrxMX2BGWiw+Z9PdOaNok7eZvYNksjI DG+kQzfE1XHXwHCgwj+DGIYxYB7ux5o2wwGKvpSE1spFn6GglfJNhjMe3R5IXIsuZk1h RmDg== X-Gm-Message-State: AOJu0Yy6Le3eDpvSvh08hzSNMJLSocueuJlzFIuO7ErUwG1I/5xsr9BW csUT/JNKj/N17E1+aQNVFAXKSyBoqoPahsOvdES6BMXDFII= X-Google-Smtp-Source: AGHT+IG1S+ZVnLodtc01R/ePHE4yLdZ8HVfGcddVowP/yXFn3qq64Mopk1V4tkYwCZMWcPPhKO6SZAwrfm9gaYLXH8A= X-Received: by 2002:a05:6102:539:b0:452:8afa:e1ac with SMTP id m25-20020a056102053900b004528afae1acmr1076002vsa.26.1695794602926; Tue, 26 Sep 2023 23:03:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Vladimir Sitnikov Date: Wed, 27 Sep 2023 09:03:11 +0300 Message-ID: Subject: Re: Regarding useObjects To: Achilleas Mantzios Cc: pgsql-jdbc@postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > so there was the option to change this to false and recompile We try doing our best to keep backward compatibility both compilation-wise and behaviour-wise. However, we treat "private fields and methods" as private, and we do not expect people would depend on them. If you have to modify sources or depend on private APIs I would suggest raising an issue or PR so it could be incorporated into the driver itself. Would you please provide a test case of what you are doing with PgArray? What is exactly the sequence of JDBC calls, the actual and the expected outcomes in your case? The mentioned "useObjects" has been removed in https://github.com/pgjdbc/pgjdbc/pull/1194 (Refactor decoding arrays) Vladimir