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 56B9ED1B50E for ; Thu, 13 Nov 2003 05:33:45 +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 66633-02 for ; Thu, 13 Nov 2003 01:33:14 -0400 (AST) Received: from candle.pha.pa.us (unknown [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 71887D1B4F9 for ; Thu, 13 Nov 2003 01:33:12 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id hAD5X9628562; Thu, 13 Nov 2003 00:33:09 -0500 (EST) From: Bruce Momjian Message-Id: <200311130533.hAD5X9628562@candle.pha.pa.us> Subject: Re: [GENERAL] Postgres 7.4 : ECPG not Thread-safe In-Reply-To: <200311131608.18106.philip@utiba.com> To: Philip Yarra Date: Thu, 13 Nov 2003 00:33:09 -0500 (EST) Cc: PostgreSQL-interfaces X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/21 X-Sequence-Number: 4579 Philip Yarra wrote: > 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. > > Yikes! I just figured updating the manual section would be a good start. I'll > 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. > > Personally I don't really like embedded SQL, and would prefer libpq, except > for one beautiful feature: it's quite portable (Informix->Sybase->PostgreSQL > with minimal re-coding). > > > 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. > > I have some of the vendors' ones to look at for ideas. > > Is the ANSI doc (freely) available? Just grab a draft as mentioned in our developers FAQ. > > 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 > connection_name' in a threaded application or suffer the consequences" would > be a good start. I guess, but there still a lot missing. I wonder if we should just find a good document on the web and point people there --- why reinvent the wheel. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073