Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 92F0337C6BA for ; Mon, 12 Nov 2007 06:21:17 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 77856-06 for ; Mon, 12 Nov 2007 06:21:00 -0400 (AST) Received: from smadev.internal.net (host3.dynacom.ondsl.gr [62.103.35.211]) by postgresql.org (Postfix) with ESMTP id 1352F37C678 for ; Mon, 12 Nov 2007 06:21:02 -0400 (AST) Received: from smadev.internal.net (localhost [127.0.0.1]) by smadev.internal.net (8.13.6/8.13.6) with ESMTP id lACAKtWx066752; Mon, 12 Nov 2007 12:20:55 +0200 (EET) (envelope-from achill@matrix.gatewaynet.com) Received: from localhost (localhost [[UNIX: localhost]]) by smadev.internal.net (8.13.6/8.13.6/Submit) id lACAKsYc066751; Mon, 12 Nov 2007 12:20:54 +0200 (EET) (envelope-from achill@matrix.gatewaynet.com) From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: pgsql-sql@postgresql.org Subject: Re: show value of backslashes in string array argument Date: Mon, 12 Nov 2007 13:20:54 +0300 User-Agent: KMail/1.9.3 Cc: "Sabin Coanda" References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200711121220.54516.achill@matrix.gatewaynet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/49 X-Sequence-Number: 29577 =D3=F4=E9=F2 =C4=E5=F5=F4=DD=F1=E1 12 =CD=EF=DD=EC=E2=F1=E9=EF=F2 2007 11:5= 1, =EF/=E7 Sabin Coanda =DD=E3=F1=E1=F8=E5: > I fond another collateral problem, because there are the different > convention to describe a varchar array item which contains backslashes, > when standard_conforming_strings =3D 'on' > > For instance, to get a string composed by just one character backslash I > can use any of the two forms: > > SELECT ARRAY[ '\' ]::varchar[]; > > or > > SELECT '{\\}'::varchar[]; > > On the other hand, standard_conforming_strings =3D 'on' let me use varchar > items with '\' format. So the first format seems to be aware of > standard_conforming_strings =3D 'on', but the second is not. > > My problem is that the java driver build arrays using the second format, > but the driver seems to be aware of standard_conforming_strings =3D 'on'. > This make inconsistence using the statement parameters, because to get the > same thing in the database I have to initialize a varchar parameter with a > string of one backslashes, but a varchar array item has to be initialized > with a string of two backslashes. > > Sabin I would recommend: a) Move to Unix b) Subscribe to pgsql-jdbc@postgresql.org > > > > ---------------------------(end of broadcast)--------------------------- > TIP 7: You can help support the PostgreSQL project by donating at > > http://www.postgresql.org/about/donate =2D-=20 Achilleas Mantzios