Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Proposed patch for error locations

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Glaesemann <grzm(at)myrealbox(dot)com>,pgsql-patches(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [PATCHES] Proposed patch for error locations
Date: 2006-03-14 02:53:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfacespgsql-patches
> from all libpq-using applications not just psql.  We could make this
> conditional on the error verbosity --- in "terse" mode the "LINE N"
> output wouldn't appear, and "at character N" still would.  Applications
> should already be expecting multiline outputs from PQerrorMessage if
> they're in non-terse mode, so this ought to be OK.  Comments?

Sounds like it'd be handy in phpPgAdmin...

In response to

pgsql-patches by date

Next:From: Simon RiggsDate: 2006-03-14 08:55:40
Subject: Re: [PATCHES] Automatic free space map filling
Previous:From: Tom LaneDate: 2006-03-13 21:28:38
Subject: Re: [PATCHES] Proposed p.tch for error locations

pgsql-interfaces by date

Next:From: Evan SherwoodDate: 2006-03-16 07:39:18
Subject: Postgres - problems with NpgsqlDataAdapter insert
Previous:From: Fangbing WuDate: 2006-03-14 01:25:46
Subject: Inherits and triggers

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group