X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9CDE5D1B52C for ; Mon, 29 Sep 2003 18:05:17 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 36959-06 for ; Mon, 29 Sep 2003 15:04:46 -0300 (ADT) Received: from lucifer.oficina (unknown [200.69.203.237]) by svr1.postgresql.org (Postfix) with ESMTP id C8C1CD1B54B for ; Mon, 29 Sep 2003 15:04:44 -0300 (ADT) Received: from [192.168.1.174] (taz.oficina [192.168.1.174] (may be forged)) (authenticated bits=0) by lucifer.oficina (8.12.9/8.12.9) with ESMTP id h8TI56v2028968; Mon, 29 Sep 2003 15:05:06 -0300 (ART) (envelope-from franco@akyasociados.com.ar) Subject: Re: SQL Syntax problem From: Franco Bruno Borghesi To: Doris Bernloehr Cc: pgsql-sql@postgresql.org In-Reply-To: <200309281443.09936.bedo7@gmx.net> References: <200309281443.09936.bedo7@gmx.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Dj/85YDDtc3wpc6w9kvD" Organization: AK y Asociados S.R.L. Message-Id: <1064858901.1509.1.camel@taz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Mon, 29 Sep 2003 15:08:21 -0300 X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/405 X-Sequence-Number: 15383 --=-Dj/85YDDtc3wpc6w9kvD Content-Type: multipart/alternative; boundary="=-RFU65tbSPy/XvvvK8A0k" --=-RFU65tbSPy/XvvvK8A0k Content-Type: text/plain Content-Transfer-Encoding: quoted-printable This kind of conditions are left or right joins, depending on which side of the equal sign you have the (+). Something like this select ... from auswahlkatalog k, INNER JOIN anspruchkorrektur a ON (k.awk_id =3D a.awk_id), LEFT JOIN beteiligter b ON (b.bet_id =3D a.bet_idemp), RIGHT JOIN v_betkorr f ON (a.ask_id =3D f.ask_id) should give you the same results. On Sun, 2003-09-28 at 09:43, Doris Bernloehr wrote: > Hello. >=20 > I've got a problem in porting the following select statement from Oracle = to=20 > Postgres, because of the characters after "b.bet_id" and "f.ask_id" in th= e=20 > where clause: (+) > I don't know what these characters mean and how I can transform these int= o=20 > PostgreSql Syntax. >=20 >=20 > select ... > from auswahlkatalog k, anspruchkorrektur a, beteiligter b, v_betkorr f > where k.awk_id =3D a.awk_id and b.bet_id(+) =3D a.bet_idemp > and a.ask_id =3D f.ask_id(+); >=20 >=20 > Hoping for help. > Doris >=20 >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >=20 --=-RFU65tbSPy/XvvvK8A0k Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable This kind of conditions are left or right joins, depending on which side of= the equal sign you have the (+).

Something like this

select        ...
from
auswahlkatalog k,
INNER JOIN anspruchkorrektur a ON (k.awk_id =3D a.awk_id),
LEFT JOIN beteiligter b ON (b.bet_id =3D a.bet_idemp),
RIGHT JOIN v_betkorr f ON (a.ask_id =3D f.ask_id)

should give you the same results.

On Sun, 2003-09-28 at 09:43, Doris Bernloehr wrote:
Hello.

I've got a problem in porting the following select statement from Oracle to=
=20
Postgres, because of the characters after "b.bet_id" and "f.=
ask_id" in the=20
where clause: (+)
I don't know what these characters mean and how I can transform these into=
=20
PostgreSql Syntax.


select        ...
from 		auswahlkatalog k, anspruchkorrektur a, beteiligter b, v_betkorr f
where       	k.awk_id =3D a.awk_id and b.bet_id(+) =3D a.bet_idemp
		and a.ask_id =3D f.ask_id(+);


Hoping for help.
Doris


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
--=-RFU65tbSPy/XvvvK8A0k-- --=-Dj/85YDDtc3wpc6w9kvD Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA/eHUV21dVnhLsBV0RAsFGAJsEz9mcmnGlT7JFU5B/QKnYRsUqLwCfYOuz nQvB3ba4RVEUOjWxUItgmu0= =w45H -----END PGP SIGNATURE----- --=-Dj/85YDDtc3wpc6w9kvD--