> --- Original Message ---
> From: "Kevin Macdonald" <[EMAIL PROTECTED]>
> To: pgsql-bugs@postgresql.org
> Sent: 1/8/07, 6:52:43 PM
> Subject: [BUGS] BUG #2875: pgAdmin III docs installed even if app is not
>
> The following bug has been logged online:
>
> Bug reference: 2875
> Log
Kevin Macdonald wrote:
> The following bug has been logged online:
>
> Bug reference: 2875
> Logged by: Kevin Macdonald
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.1
> Operating system: Windows XP
> Description:pgAdmin III docs installed even if app is
Tom Lane wrote:
> This is closely related to the discussion a couple weeks ago about how
> a LEFT JOIN could produce nulls in an output column that was labeled as
> having a non-null-domain type. We haven't figured out what is a sane
> behavior for that case, either. I'm beginning to think that
Tom,
On Wed, Jan 03, 2007 at 08:02:34PM -0500, Tom Lane wrote:
> No, Dmitry has it right: the man page is mistaken. You can still get
> silent mode but you have to use the long-form option (--silent-mode=1).
>
> I've corrected the documentation error in CVS.
I think that you have forgotten to
The following bug has been logged online:
Bug reference: 2875
Logged by: Kevin Macdonald
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Windows XP
Description:pgAdmin III docs installed even if app is not
Details:
The the documentation
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> Perhaps a means to mark the record as being null, other than setting all
> the fields to null?
We could probably bypass the call of the domain input function, thereby
avoiding the elog, but the point remains: if we do that, then we have
a NOT-NULL-const
On Mon, Jan 08, 2007 at 10:27:15AM -0500, Tom Lane wrote:
> "Jonathan Hull" <[EMAIL PROTECTED]> writes:
> > The key feature for the error is that when a result structure (eg : pg_foo)
> > is defined with a domain type that is not null, only PG 8.2 errors if the
> > result is an empty set.
>
> The
