Patrick Welche wrote:
> On Fri, May 20, 2005 at 11:12:54PM -0400, Bruce Momjian wrote:
> > Added to TODO:
> >
> > * Allow INET + INT4/INT8 to increment the host part of the address, or
> > throw an error on overflow
> >
> > I have not heard any use-case for adding to the network value i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been playing with the new bitmap stuff, and so far, it seems
to be working fairly well. I have two very minor complaints, however.
First, some of my queries have a large number of "OR" conditions,
and this is where the bitmap gets used a lot. H
On Thu, 19 May 2005, Tom Lane wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
* I'm inclined to think that the "gid" identifiers for prepared
transactions ought to be SQL identifiers (names), not string literals.
Was there a particular reason for making them strings?
Sure. No Reason.
On Friday 20 May 2005 18:14, Tom Lane wrote:
> Bruce Momjian writes:
> > As I remember, you said two-phase wasn't 100% reliable and we just
> > needed a way to report failures.
>
> [ Shrug... ] I remain of the opinion that 2PC is a solution in search
> of a problem, because it does not solve the
minor nit: the null attribute should take XMLSchema boolean type values:
{true, false, 1, 0}
More importantly, how do you handle array or record type fields? If they
are just opaque text I don't think that's what I at least would want
from XML output routines.
cheers
andrew
Christopher K
