Tom,
I tried to build a simple test case and I couldn't reproduce either.
I'm still actively working with that database, though-- If I run into it
again, and can reproduce a condensed case, I'll definitely submit it. It
sounds like views are being improved a good deal in 7.1, so perhaps my
oddi
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>
> > I've suggested a couple of times that since we include install-sh in our
> > distro anyway, it's pointless and unnecessarily risky to go looking for
> > a platform-supplied install program. However, I could never quite get
>
Mark Stosberg <[EMAIL PROTECTED]> writes:
>I'm running Postgres 7.0.2 and have run into a curious situation. I
> got a back a null value in a select on VIEW that is defined as not
> allowing that column to be null.
I think this is an artifact of the curious (not to say broken)
implementation
"Primoz" <[EMAIL PROTECTED]> writes:
> If I try to dump database with sequences which have "Uppercase" names it
> dumps it like this:
> CREATE SEQUENCE "Uppercase";
> CREATE TABLE "Table" (
> "ID" int4 not null default nextval('Uppercase':something),
> );
This is fixed in 7.1. I don't think th
This is a known problem. We don't have a fix yet.
> Hi,
> We think we have found a problem when deleting and inserting in
> the same transaction with constraints deferred:
>
>
> machine=> create table foo (bar int4 primary key, ref int4 references foo
> deferrable
Hi,
We think we have found a problem when deleting and inserting in
the same transaction with constraints deferred:
machine=> create table foo (bar int4 primary key, ref int4 references foo
deferrable);
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index
I think there is a bug in pgDump..
If I try to dump database with sequences which have "Uppercase" names it
dumps it like this:
CREATE SEQUENCE "Uppercase";
CREATE TABLE "Table" (
"ID" int4 not null default nextval('Uppercase':something),
);
And it do not work until I manualy change it to
CRE
Hello,
I'm running Postgres 7.0.2 and have run into a curious situation. I
got a back a null value in a select on VIEW that is defined as not
allowing that column to be null. Here's a screenshot:
marvel=> \d shipments;
View= shipments
Query = SELECT "web_data"."shipment_id", "web_data"
At 13:24 08/03/01 -0500, [EMAIL PROTECTED] wrote:
>Rahul Tyagi ([EMAIL PROTECTED]) reports a bug with a severity of 2
>The lower the number the more severe it is.
>
>Short Description
>createStatement(int,int) of interface Statement not implemented
>
>Long Description
>createStatement(int,int) of
At 13:22 08/03/01 -0500, [EMAIL PROTECTED] wrote:
>Rahul Tyagi ([EMAIL PROTECTED]) reports a bug with a severity of 2
>The lower the number the more severe it is.
>
>Short Description
>absolute(int rownumber) method not implemented as per Sun guidlines
>
>Long Description
>absolute(int rownumber)
10 matches
Mail list logo