I am using PGSQL 7.1RC1.
CREATE TABLE "test" (
"id" int4 DEFAULT nextval('"test_id_seq"'::text) NOT NULL,
"val" int4,
CONSTRAINT "test_pkey" PRIMARY KEY ("id")
);
CREATE TABLE test_1 (
) INHERITS (test);
Do:
INSERT INTO "test_1" (
will trillich wrote:
>
> um, what's "application layer" mean? :)
>
sorry - I mean customise queries in the application itself. I tend to
build a database abstraction layer which does all this stuff for me.
- Richard Huxton
---(end of broadcast)-
Christian Marschalek wrote:
>
> Hi all of you! :o)
>
> I guess I do have to shut down the database before shutting down the
> linux box?
> How would I accomplish this?
> Just by killing the postmaster per pid?
Be careful with that - there's a page on this in the admin's guide. You
should have a
Andrey Y. Mosienko writes:
> I am using PGSQL 7.1RC1.
>
> CREATE TABLE "test" (
>"id" int4 DEFAULT nextval('"test_id_seq"'::text) NOT NULL,
>"val" int4,
>CONSTRAINT "test_pkey" PRIMARY KEY ("id")
> );
>
> CREATE TABLE test_1 (
> ) INHERITS (test);
>
> Do:
> INSERT INTO "test_1" ("id",
Hi there :o)
Would you mind replying with a list of your favourite programs with
guis? (for postgresql of cause;)
Tia!
(and thanks for the answers to my last question, about shutting down the
database)
Regards, Chris
---(end of broadcast)---
T
Hi,
Is it technically possible for there to be a "select for insert"? e.g.
other select for inserts with the same effective where clause will block
even if no rows are there yet.
Or should select .. for update actually work that way? I think it's
probably too difficult to implement it tho.
Wha
Lincoln Yeoh <[EMAIL PROTECTED]> writes:
> Is it technically possible for there to be a "select for insert"? e.g.
> other select for inserts with the same effective where clause will block
> even if no rows are there yet.
What would you define as the "same effective where clause"? Shades of
the
For some reason, probably because I'm not understanding very well, I'm
getting some duplicated rows for this query (below).
My understanding is that "group by" brings all the rows together where the
indicated columns are equal and then applies the aggregate to the column
indicated; in this case:
"Matt Friedman" <[EMAIL PROTECTED]> writes:
> What am I missing? I'm not seeing why this query doesn't group everything
> and then return unique rows.
Since you didn't show an example of the input and output, it's hard to
tell what your gripe is ... but I'll venture that you didn't want to
group
Yeah, it was right under my nose. Figured it out just before I got your
email.
Thank you.
Matt Friedman
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Matt Friedman" <[EMAIL PROTECTED]>
Cc: "PgSql General List" <[EMAIL PROTECTED]>
Sent: Saturday, March 24, 2001 1:34 PM
Well, this wasn't the posting I had in mind, but it's
even better. Didn't know that 7.1 was so well
documented. Thanks, Developers.
For anyone else's benefits here's the URL for the CVS
fetch.
http://www.postgresql.org/devel-corner/docs/postgres/cvs.html
And here's the URL for the install
Hi!
I can't find the desciption of "views" in the PostgreSQL docs.
Could somebody please point me out or explain database views to me?
Thanks and regards Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister
On Sun, 25 Mar 2001, Christian Marschalek wrote:
> I can't find the desciption of "views" in the PostgreSQL docs.
> Could somebody please point me out or explain database views to me?
http://www.postgresql.org/users-lounge/docs/7.0/user/sql-createview.htm
This is a good start to see how they ar
On Fri, Mar 23, 2001 at 05:28:24PM -0500, Gregory Wood wrote:
> Well, the problem is that currval() is the value last inserted by *that*
> backend into the database. The reasoning for this is simple:
okay ... :)
> If Paul just inserted a record and wants to find out what sequence value was
> ins
14 matches
Mail list logo