X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CD67DD1B504 for ; Thu, 13 Nov 2003 05:08:56 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 51848-09 for ; Thu, 13 Nov 2003 01:08:26 -0400 (AST) Received: from cpc-gw2.cpc.net.au (unknown [210.9.248.93]) by svr1.postgresql.org (Postfix) with ESMTP id 5784FD1B535 for ; Thu, 13 Nov 2003 01:08:21 -0400 (AST) Received: from utiba.com (ser1.cpc.net.au [192.168.0.19]) by Utiba Mail Gateway (2.2.2) with ESMTP id hAD58K831720; Thu, 13 Nov 2003 16:08:21 +1100 Received: from pc37.cpc.net.au (pc37.cpc.net.au [192.168.0.37]) by Utiba Mail Thingy (0.0.2) with ESMTP id hAD58K600976; Thu, 13 Nov 2003 16:08:20 +1100 Content-Type: text/plain; charset="iso-8859-1" From: Philip Yarra Organization: Utiba Pty Ltd To: Bruce Momjian Subject: Re: [GENERAL] Postgres 7.4 : ECPG not Thread-safe Date: Thu, 13 Nov 2003 16:08:18 +1100 User-Agent: KMail/1.4.3 Cc: PostgreSQL-interfaces References: <200311130447.hAD4ldZ23273@candle.pha.pa.us> In-Reply-To: <200311130447.hAD4ldZ23273@candle.pha.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200311131608.18106.philip@utiba.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/20 X-Sequence-Number: 4578 On Thu, 13 Nov 2003 03:47 pm, Bruce Momjian wrote: > Philip Yarra wrote: > > I'm willing to have a go at updating the doco. Can someone point me to a > > guide to getting started with the markup we use? > > Great, but be warned --- the work is huge.=20=20 Yikes! I just figured updating the manual section would be a good start. I'= ll=20 deal with *huge* later. > Let me also add > that it is totally cool! It doesn't look all that friendly, but once > you start coding in it, and pass variables in and out of queries, it > takes on amazing power and has amazing clarity.=20=20 Personally I don't really like embedded SQL, and would prefer libpq, except= =20 for one beautiful feature: it's quite portable (Informix->Sybase->PostgreSQ= L=20 with minimal re-coding).=20 > Anyway, I think you can grab any ANSI SQL enbedded document and get > ideas. You can look at vendors docs because those are going to be very > similar, and you can look at the ANSI standard for ideas.=20=20 I have some of the vendors' ones to look at for ideas. Is the ANSI doc (freely) available?=20 > that really shows the power of ecpg --- right now, our docs don't do it > justice. Agreed. I'll see what I can do. I figure just adding "always use 'AT=20 connection_name' in a threaded application or suffer the consequences" woul= d=20 be a good start.=20 Regards, Philip.