From: | Philip Yarra <philip(at)utiba(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-interfaces <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] Postgres 7.4 : ECPG not Thread-safe |
Date: | 2003-11-13 05:08:18 |
Message-ID: | 200311131608.18106.philip@utiba.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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?
> 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.
Regards, Philip.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-11-13 05:33:09 | Re: [GENERAL] Postgres 7.4 : ECPG not Thread-safe |
Previous Message | Bruce Momjian | 2003-11-13 04:48:43 | Re: [GENERAL] Postgres 7.4 : ECPG not Thread-safe |