Undeliverable Message - Mailing list pgsql-general
| From | |
|---|---|
| Subject | Undeliverable Message |
| Date | |
| Msg-id | vines.n4,8+eQzkqA@SFRA0046. Whole thread Raw |
| List | pgsql-general |
To: ISMTP@SFRA0046@Servers[<pgsql-general-digest@hub.org>]
Cc:
Subject: pgsql-general-digest V1 #220
Message not delivered to recipients below. Press F1 for help with VNM
error codes.
VNM3043: DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST
VNM3043 -- MAILBOX IS FULL
The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).
When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.
---------------------- Original Message Follows ----------------------
pgsql-general-digest Friday, February 12 1999 Volume 01 : Number 220
Index:
Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
unsubscribe pgsql-general
unsubscribe pgsql-general
Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Re: Problems compiling
Undeliverable Message
----------------------------------------------------------------------
Date: Thu, 11 Feb 1999 21:20:55 -0800 (PST)
From: dustin sallings <dustin@spy.net>
Subject: Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
On Thu, 11 Feb 1999, Stephan Doliov wrote:
So, are we serious about this? Should we start up a list for
details?
//
// > Since we are tossing ideas around, here is my two cents.
// > .1c In order not to worry about royalties we can donate proceeds to
// > PostgreSQL.
// Amen/Bravo! This would truly be in the spirit of PostgreSQL
//
// Regarding the books contents. I think
// I. Section 1 - Intro
// 1. Brief Overview History
// 2. Getting and Installing
// 3. Setting up a Database
// 4. Maintaining a Database
// II. Section II - Making it work
// 1. Postgres' type system
// 2. Triggers & Functions
// 3. Embedded Scripting Languages
// a) pl/pgsql
// etc.
// 4. External access to postgres
// a) libpq
// b) libpq++
// c) odbc
// etc.
// 5. Interfacing PostgreSQL to the Web
// a) perl
// b) php3
// c) pygreSQL
// others
// III. Reference and Tekkie Stuff
// 1. The built-in functions
// 2. Query Optimization
// 3. Postmaster tuning & performance issues
// IV. New Features
// This would be a section where people could insert information related to
// the latest release. Much like law reports have addenda inserts at the
// back.
//
// my $0.02
//
// steve doliov
//
//
//
- --
Principal Member Technical Staff, beyond.com The world is watching America,
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
| Key fingerprint L______________________________________________ and America is watching TV. __
------------------------------
Date: Fri, 12 Feb 1999 01:29:55 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
Subject: Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
On Thu, 11 Feb 1999, dustin sallings wrote:
> On Thu, 11 Feb 1999, Stephan Doliov wrote:
>
> So, are we serious about this? Should we start up a list for
> details?
Like, pgsql-docs@postgresql.org :) How much of what is already
done by the Docs Team pertinent to all this, and, if not, why not? If our
existing manuals don't make good documentation, then why not, and
shouldn't those be fixed too?
> > //
> // > Since we are tossing ideas around, here is my two cents.
> // > .1c In order not to worry about royalties we can donate proceeds to
> // > PostgreSQL.
> // Amen/Bravo! This would truly be in the spirit of PostgreSQL
> //
> // Regarding the books contents. I think
> // I. Section 1 - Intro
> // 1. Brief Overview History
> // 2. Getting and Installing
> // 3. Setting up a Database
> // 4. Maintaining a Database
> // II. Section II - Making it work
> // 1. Postgres' type system
> // 2. Triggers & Functions
> // 3. Embedded Scripting Languages
> // a) pl/pgsql
> // etc.
> // 4. External access to postgres
> // a) libpq
> // b) libpq++
> // c) odbc
> // etc.
> // 5. Interfacing PostgreSQL to the Web
> // a) perl
> // b) php3
> // c) pygreSQL
> // others
> // III. Reference and Tekkie Stuff
> // 1. The built-in functions
> // 2. Query Optimization
> // 3. Postmaster tuning & performance issues
> // IV. New Features
> // This would be a section where people could insert information related to
> // the latest release. Much like law reports have addenda inserts at the
> // back.
> //
> // my $0.02
> //
> // steve doliov
> //
> //
> //
>
> --
> Principal Member Technical Staff, beyond.com The world is watching America,
> pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
> | Key fingerprint > L______________________________________________ and America is watching TV. __
>
>
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
------------------------------
Date: Thu, 11 Feb 1999 21:32:40 -0800 (PST)
From: dustin sallings <dustin@spy.net>
Subject: Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
On Fri, 12 Feb 1999, The Hermit Hacker wrote:
// Like, pgsql-docs@postgresql.org :) How much of what is already
// done by the Docs Team pertinent to all this, and, if not, why not?
// If our existing manuals don't make good documentation, then why not,
// and shouldn't those be fixed too?
It's not that the docs are bad, it's just that they're not on a
shelf. :)
// > > //
// > // > Since we are tossing ideas around, here is my two cents.
// > // > .1c In order not to worry about royalties we can donate proceeds to
// > // > PostgreSQL.
// > // Amen/Bravo! This would truly be in the spirit of PostgreSQL
// > //
// > // Regarding the books contents. I think
// > // I. Section 1 - Intro
// > // 1. Brief Overview History
// > // 2. Getting and Installing
// > // 3. Setting up a Database
// > // 4. Maintaining a Database
// > // II. Section II - Making it work
// > // 1. Postgres' type system
// > // 2. Triggers & Functions
// > // 3. Embedded Scripting Languages
// > // a) pl/pgsql
// > // etc.
// > // 4. External access to postgres
// > // a) libpq
// > // b) libpq++
// > // c) odbc
// > // etc.
// > // 5. Interfacing PostgreSQL to the Web
// > // a) perl
// > // b) php3
// > // c) pygreSQL
// > // others
// > // III. Reference and Tekkie Stuff
// > // 1. The built-in functions
// > // 2. Query Optimization
// > // 3. Postmaster tuning & performance issues
// > // IV. New Features
// > // This would be a section where people could insert information related to
// > // the latest release. Much like law reports have addenda inserts at the
// > // back.
// > //
// > // my $0.02
// > //
// > // steve doliov
// > //
// > //
// > //
// >
// > --
// > Principal Member Technical Staff, beyond.com The world is watching America,
// > pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
// > | Key fingerprint // > L______________________________________________ and America is watching TV. __
// >
// >
//
// Marc G. Fournier
// Systems Administrator @ hub.org
// primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
//
//
- --
Principal Member Technical Staff, beyond.com The world is watching America,
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
| Key fingerprint L______________________________________________ and America is watching TV. __
------------------------------
Date: Fri, 12 Feb 1999 11:22:21 +0530 (IST)
From: Purushottam Dayma <pdayma@jln2.mahyco.com>
Subject: unsubscribe pgsql-general
unsubscribe pgsql-general
------------------------------
Date: Fri, 12 Feb 1999 11:34:48 +0500 (GMT+0500)
From: Purushottam S Dayma <dayma@mahjln.mahyco.com>
Subject: unsubscribe pgsql-general
unsubscribe pgsql-general
------------------------------
Date: Thu, 11 Feb 1999 22:52:25 -0800
From: "Rudy Gireyev" <rgireyev@cnmnetwork.com>
Subject: Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Additionally manuals tend to be more of a reference whereas a book is
primarily a tutorial, then at the end it can contain reference type material.
If the book were to be written it would need complete and working examples
followed by the exact result for example.
Therefore I think it's a whole different animal and requires a list of its own.
Rudy
Date sent: Thu, 11 Feb 1999 21:32:40 -0800 (PST)
From: dustin sallings <dustin@spy.net>
To: The Hermit Hacker <scrappy@hub.org>
Copies to: Stephan Doliov <statsol@statsol.com>, pgsql-novice@postgreSQL.org,
pgsql-general@postgreSQL.org
Subject: Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
> On Fri, 12 Feb 1999, The Hermit Hacker wrote:
>
> // Like, pgsql-docs@postgresql.org :) How much of what is already
> // done by the Docs Team pertinent to all this, and, if not, why not?
> // If our existing manuals don't make good documentation, then why not,
> // and shouldn't those be fixed too?
>
> It's not that the docs are bad, it's just that they're not on a
> shelf. :)
>
> // > > //
> // > // > Since we are tossing ideas around, here is my two cents.
> // > // > .1c In order not to worry about royalties we can donate proceeds to
> // > // > PostgreSQL.
> // > // Amen/Bravo! This would truly be in the spirit of PostgreSQL
> // > //
> // > // Regarding the books contents. I think
> // > // I. Section 1 - Intro
> // > // 1. Brief Overview History
> // > // 2. Getting and Installing
> // > // 3. Setting up a Database
> // > // 4. Maintaining a Database
> // > // II. Section II - Making it work
> // > // 1. Postgres' type system
> // > // 2. Triggers & Functions
> // > // 3. Embedded Scripting Languages
> // > // a) pl/pgsql
> // > // etc.
> // > // 4. External access to postgres
> // > // a) libpq
> // > // b) libpq++
> // > // c) odbc
> // > // etc.
> // > // 5. Interfacing PostgreSQL to the Web
> // > // a) perl
> // > // b) php3
> // > // c) pygreSQL
> // > // others
> // > // III. Reference and Tekkie Stuff
> // > // 1. The built-in functions
> // > // 2. Query Optimization
> // > // 3. Postmaster tuning & performance issues
> // > // IV. New Features
> // > // This would be a section where people could insert information related to
> // > // the latest release. Much like law reports have addenda inserts at the
> // > // back.
> // > //
> // > // my $0.02
> // > //
> // > // steve doliov
> // > //
> // > //
> // > //
> // >
> // > --
> // > Principal Member Technical Staff, beyond.com The world is watching America,
> // > pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
> // > | Key fingerprint > // > L______________________________________________ and America is watching TV. __
> // >
> // >
> //
> // Marc G. Fournier
> // Systems Administrator @ hub.org
> // primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
> //
> //
>
> --
> Principal Member Technical Staff, beyond.com The world is watching America,
> pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
> | Key fingerprint > L______________________________________________ and America is watching TV. __
>
>
>
------------------------------
Date: Thu, 11 Feb 1999 22:54:51 -0800 (PST)
From: Felix Morley Finch <felix@crowfix.com>
Subject: Re: Problems compiling
> configure: error: installation or configuration problem: C++ compiler cannot create executables.
My memory of the last couple of egcs/glibc installs is that the
/lib/cpp symlink is not updated, and root had better have umask 022 or
permissions don't get set right. Even with umask 022,
/usr/lib/gcc-lib/... has an include directory owned by whoever did the
compiling, and permissions also unchanged.
And I do remember getting that strange message, but I'm not at all
sure if it was caused by the mis-behaving install.
(I sent email to the maintainers, but they alleged it was my fault,
and it hasn't been fixed in the year since then.)
- --
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
PGP I've found a solution to Fermat's Last Theorem but I see I've run out of room o
------------------------------
Date: Fri, 12 Feb 99 9:09:16 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message
To: ISMTP@SFRA0046@Servers[<pgsql-general-digest@hub.org>]
Cc:
Subject: pgsql-general-digest V1 #219
Message not delivered to recipients below. Press F1 for help with VNM
error codes.
VNM3043: DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST
VNM3043 -- MAILBOX IS FULL
The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).
When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.
- ---------------------- Original Message Follows ----------------------
pgsql-general-digest Thursday, February 11 1999 Volume 01 : Number 219
Index:
Re: [GENERAL] A book for PgSQL? A need? yes? no?
Re: [GENERAL] A book for PgSQL? A need? yes? no?
Re: [GENERAL] A book for PgSQL? A need? yes? no?
Re: [GENERAL] Select max field
Re: [GENERAL] A book for PgSQL? A need? yes? no?
Re: [GENERAL] A book for PgSQL? A need? yes? no?
Problem with table,field names.
Index Problem
Re: [GENERAL] Problem with table,field names.
Installer PostGres..
Off-Topic, but Important [Fwd: Free Speech 0 ; US West 1]
Lawyers a go go.
no swap space
Re: [GENERAL] Installer PostGres..
Re: [GENERAL] Installer PostGres..
Re: Lawyers a go go.
Conditioned access to a database
need help separating a field
Re: [GENERAL] need help separating a field
Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
unsubscribe
Problems compiling
RES: [GENERAL] Conditioned access to a database
- ----------------------------------------------------------------------
Date: Thu, 11 Feb 1999 02:35:01 -0500 (EST)
From: Bob Dusek <bobd@palaver.net>
Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Amen. A book would be really cool. I would think that it would open up
the PostgreSQL market a bit more, too. A book on the shelf is
advertising.
A new, good, recommended book is great advertising.
Bob
On Thu, 11 Feb 1999, Robert Chalmers wrote:
> Just wondering if there is a book specifically written around PgSQL, and if not, would anyone want one? You know, a
thinglike "A Guide To PgSQL". Not too heavy, maybe in parts. User + Advanced + ODBC ?
>
> What do you think?
>
> Robert
>
- ------------------------------
Date: Wed, 10 Feb 1999 23:53:45 -0800 (PST)
From: dustin sallings <dustin@spy.net>
Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
On Thu, 11 Feb 1999, Bob Dusek wrote:
The problem with writing a book on Postgres is that it's still
being developed. Before a book could be published, it'd be mostly
obsolete. I certainly would like the exercise of assembling one, but I
really hate getting obsolete books. This happened to me when I bought my
first Java book. I took it home and almost nothing in it worked. :) Of
course, Postgres is changing in a compatible way, but the new stuff that's
introduced *dramatically* changes the way people code. pl/pgsql is a
great example of this. There's stuff that's done in pl/pgsql that
previously had to be done C in a really complicated way, or you had to sit
around wishing for. This will change yet again when there's fk/pk
constraints and such. Chances are, there'll be a lot of neat stuff that
will need to be included in a book before a book can be finished. :)
I'm sure there's enough documentation lying around to make a
decent book if we want to put it together. Figuring out royalties could
be kinda difficult. :)
// Amen. A book would be really cool. I would think that it would open up
// the PostgreSQL market a bit more, too. A book on the shelf is
// advertising.
//
// A new, good, recommended book is great advertising.
//
// Bob
//
// On Thu, 11 Feb 1999, Robert Chalmers wrote:
//
// > Just wondering if there is a book specifically written around PgSQL, and if not, would anyone want one? You know,
athing like "A Guide To PgSQL". Not too heavy, maybe in parts. User + Advanced + ODBC ?
// >
// > What do you think?
// >
// > Robert
// >
//
//
//
- - --
Principal Member Technical Staff, beyond.com The world is watching America,
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
| Key fingerprint L______________________________________________ and America is watching TV. __
- ------------------------------
Date: Thu, 11 Feb 1999 00:20:01 -0800
From: Adam Haberlach <haberlaa@ricochet.net>
Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
On Wed, Feb 10, 1999 at 11:53:45PM -0800, dustin sallings wrote:
> On Thu, 11 Feb 1999, Bob Dusek wrote:
>
> I'm sure there's enough documentation lying around to make a
> decent book if we want to put it together. Figuring out royalties could
> be kinda difficult. :)
Agreed. If anything, I would just polish up the online docs,
publish them profesionally, and use the profits to fund development,
pay for websites, or whatever.
- ------------------------------
Date: Thu, 11 Feb 1999 03:32:01 -0500 (EST)
From: Bob Dusek <bobd@palaver.net>
Subject: Re: [GENERAL] Select max field
hey Bob et al,
I guess I'm going to have to eat a bit of crow, here.
The query I gave you was wrong, it won't work. Here are a couple that will,
for the database example that I gave you:
This one gives you id_no and max(tval) pairs:
select id_no, max(tval) from tablename group by id_no;
This one gives you the id_no, tval, tnum set for the max(tval) of the entire table:
select id_no, tval, tnum from tablename where tval (kind of a worthless query for your purposes, or so it
seems)
Sorry for the misleading email, earlier.
Bob
> I am looking for a way to determine the largest value of a number of fields
> in a tuple.
>
> Example: In a table with the fields id_no, t1, t2 ,t3 ,t4 ,t5
> Select the id_no and the greatest value from fields t1, t2, t3,
> t4, t5.
>
> I have tried the following, but with no success:
>
> select id_no, max(t1, t2, t3, t4, t5) from table_1 ;
What do the fields t1, t2, t3, t4, and t5 represent?
Do they all represent very different "real world" things, but are merely of the same
same type (like int4 or something)?
This seems to be a "style" issue to me. I would suggest creating a table that
contains only the fields: id_no, tval, tnum.
Then, for each id_no that you are tracking, you would have 5 entries in the
table. For example's sake, let's say id_no t4
id_no | tval | tnum
- - -------------------------
33 | 10 | 1
33 | 20 | 2
33 | 30 | 3
33 | 40 | 4
33 | 50 | 5
Then, to select the max for id_no 33 you would perform the following query:
select id_no, max(tval), tnum from tablename where id_no
The query would return:
id_no | max | tnum
- - ------------------------
33 | 50 | 5
To select the max for all id_no's you would simply drop the "where id_no clause from your query.
I haven't tested this, yet. But, I'm pretty sure it would work.
HTH,
Bob
>
> Anyone have any suggestions?
>
> Thanks in advance for any assistance.
>
> Regards - Bob
>
>
>
- ------------------------------
Date: Thu, 11 Feb 1999 00:31:33 -0800
From: rgireyev@cnmnetwork.com
Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Since we are tossing ideas around, here is my two cents.
.1c In order not to worry about royalties we can donate proceeds to
PostgreSQL.
.1c There is stuff that changes and there is stuff that remains the same.
Installation, database creation, db administration, function creation etc ... are
pretty uniform so they can be covered in the "stay put" section. The stuff that
is more dynamic can be smacked in the "emerging technologies" section :-)
so that the reader can simply read up on that particular technology or buy a
whole new book.
Rudy
Date sent: Wed, 10 Feb 1999 23:53:45 -0800 (PST)
From: dustin sallings <dustin@spy.net>
To: Bob Dusek <bobd@palaver.net>
Copies to: Robert Chalmers <robert@chalmers.com.au>, sql@chalmers.com.au,
pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
> On Thu, 11 Feb 1999, Bob Dusek wrote:
>
> The problem with writing a book on Postgres is that it's still
> being developed. Before a book could be published, it'd be mostly
> obsolete. I certainly would like the exercise of assembling one, but I
> really hate getting obsolete books. This happened to me when I bought my
> first Java book. I took it home and almost nothing in it worked. :) Of
> course, Postgres is changing in a compatible way, but the new stuff that's
> introduced *dramatically* changes the way people code. pl/pgsql is a
> great example of this. There's stuff that's done in pl/pgsql that
> previously had to be done C in a really complicated way, or you had to sit
> around wishing for. This will change yet again when there's fk/pk
> constraints and such. Chances are, there'll be a lot of neat stuff that
> will need to be included in a book before a book can be finished. :)
>
> I'm sure there's enough documentation lying around to make a
> decent book if we want to put it together. Figuring out royalties could
> be kinda difficult. :)
>
> // Amen. A book would be really cool. I would think that it would open up
> // the PostgreSQL market a bit more, too. A book on the shelf is
> // advertising.
> //
> // A new, good, recommended book is great advertising.
> //
> // Bob
> //
> // On Thu, 11 Feb 1999, Robert Chalmers wrote:
> //
> // > Just wondering if there is a book specifically written around PgSQL, and if not, would anyone want one? You
know,a thing like "A Guide To PgSQL". Not too heavy, maybe in parts. User + Advanced + ODBC ?
> // >
> // > What do you think?
> // >
> // > Robert
> // >
> //
> //
> //
>
> --
> Principal Member Technical Staff, beyond.com The world is watching America,
> pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
> | Key fingerprint > L______________________________________________ and America is watching TV. __
>
>
>
- ------------------------------
Date: Thu, 11 Feb 1999 00:55:38 -0800 (PST)
From: dustin sallings <dustin@spy.net>
Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
On Thu, 11 Feb 1999 rgireyev@cnmnetwork.com wrote:
// Since we are tossing ideas around, here is my two cents.
// .1c In order not to worry about royalties we can donate proceeds to
// PostgreSQL.
Does anyone on this list have any experience with putting a book
together? I've read O'Reilly's requirements and procedures, but that's
about as far as I've gone. It'd be a fun community effort I think.
// .1c There is stuff that changes and there is stuff that remains the same.
// Installation, database creation, db administration, function creation etc ... are
// pretty uniform so they can be covered in the "stay put" section. The stuff that
// is more dynamic can be smacked in the "emerging technologies" section :-)
// so that the reader can simply read up on that particular technology or buy a
// whole new book.
//
// Rudy
//
// Date sent: Wed, 10 Feb 1999 23:53:45 -0800 (PST)
// From: dustin sallings <dustin@spy.net>
// To: Bob Dusek <bobd@palaver.net>
// Copies to: Robert Chalmers <robert@chalmers.com.au>, sql@chalmers.com.au,
// pgsql-general@postgreSQL.org
// Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
//
// > On Thu, 11 Feb 1999, Bob Dusek wrote:
// >
// > The problem with writing a book on Postgres is that it's still
// > being developed. Before a book could be published, it'd be mostly
// > obsolete. I certainly would like the exercise of assembling one, but I
// > really hate getting obsolete books. This happened to me when I bought my
// > first Java book. I took it home and almost nothing in it worked. :) Of
// > course, Postgres is changing in a compatible way, but the new stuff that's
// > introduced *dramatically* changes the way people code. pl/pgsql is a
// > great example of this. There's stuff that's done in pl/pgsql that
// > previously had to be done C in a really complicated way, or you had to sit
// > around wishing for. This will change yet again when there's fk/pk
// > constraints and such. Chances are, there'll be a lot of neat stuff that
// > will need to be included in a book before a book can be finished. :)
// >
// > I'm sure there's enough documentation lying around to make a
// > decent book if we want to put it together. Figuring out royalties could
// > be kinda difficult. :)
// >
// > // Amen. A book would be really cool. I would think that it would open up
// > // the PostgreSQL market a bit more, too. A book on the shelf is
// > // advertising.
// > //
// > // A new, good, recommended book is great advertising.
// > //
// > // Bob
// > //
// > // On Thu, 11 Feb 1999, Robert Chalmers wrote:
// > //
// > // > Just wondering if there is a book specifically written around PgSQL, and if not, would anyone want one? You
know,a thing like "A Guide To PgSQL". Not too heavy, maybe in parts. User + Advanced + ODBC ?
// > // >
// > // > What do you think?
// > // >
// > // > Robert
// > // >
// > //
// > //
// > //
// >
// > --
// > Principal Member Technical Staff, beyond.com The world is watching America,
// > pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
// > | Key fingerprint // > L______________________________________________ and America is watching TV. __
// >
// >
// >
//
//
//
//
- - --
Principal Member Technical Staff, beyond.com The world is watching America,
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
| Key fingerprint L______________________________________________ and America is watching TV. __
- ------------------------------
Date: Thu, 11 Feb 1999 12:45:08 +0200 (EET)
From: Blashko Alexander <black@lins.ospu.odessa.ua>
Subject: Problem with table,field names.
Hi everybody!
In the Odessa University we have developed Information System
by using Linux (Red hat 5.2), Postgres 6.2, SWI Prolog.
Now we try to use Postgres 6.4, but have folowing problem:
create table TEST ( Name text);
We use Locale-support ( koi8r)
System Postgres 6.2 reform names of table and fields in low case.
For example:
create table TEST ( NAME text)
->
test name
^^^^ ^^^^
But in Postgres 6.4 system doesnt reform this names.
We need use old property, because many our applications use
case unsensibility property.
Please, answer, where can we find in src-code this property.
Thank you for you answer.
- ------------------------------
Date: Thu, 11 Feb 1999 23:32:37 +0800
From: Bennett Yip <benyip@netvigator.com>
Subject: Index Problem
I found that postgresql cannot create a index with more than 7 elements.
Can anyone teach me how to create a index with 8 elements?
Bennett
- ------------------------------
Date: Thu, 11 Feb 1999 19:03:57 +0300 (MSK)
From: Oleg Broytmann <phd@sun.med.ru>
Subject: Re: [GENERAL] Problem with table,field names.
On Thu, 11 Feb 1999, Blashko Alexander wrote:
> create table TEST ( NAME text)
create table "TEST" ( "NAME" text)
Use double quotations - it is standard SQL feature.
Oleg.
- - ----
Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net
Programmers don't die, they just GOSUB without RETURN.
- ------------------------------
Date: Thu, 11 Feb 1999 08:23:53 -0800 (PST)
From: Sandrine <schypre@yahoo.fr>
Subject: Installer PostGres..
>
> Bonjour,
> J'ai qqs pbs pour installer postgres. Apres avoir FINALEMENT reussi a
> telecharger la verion. Je me suis attachee a l installer.
> J ai donc fait un
> gunzip -c ~/InstallPostGres/postgresql-6.4.2.tar.gz | tar xvf -
>
> Je lance le .configure dans
> /usr/src/pgsql/postgresql-6.4.2/src
>
> Et voila ce qui me dit... le vilan :)
> [postgres@localhost src]$ ./configure
> loading cache ./config.cache
> checking host system type... i586-pc-linux-gnu
> checking echo setting...
> checking setting template to... linux_i386
> checking setting USE_LOCALE... disabled
> checking setting CYR_RECODE... disabled
> checking setting MULTIBYTE... disabled
> checking setting DEF_PGPORT... 5432
> checking setting USE_TCL... disabled
> checking setting USE_PERL... disabled
> checking setting USE_ODBC... disabled
> checking setting ASSERT CHECKING... disabled
> checking for gcc... gcc
> checking whether the C compiler (gcc -O2 ) works...
yes
> checking whether the C compiler (gcc -O2 ) is a
> cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking how to run the C preprocessor... gcc -E
> checking whether gcc needs -traditional... no
> - setting CPPFLAGS> - setting LDFLAGS> checking for c++... no
> checking for g++... no
> checking for gcc... gcc
> checking whether the C++ compiler (gcc ) works... no
> configure: error: installation or configuration
> problem: C++ compiler
> cannot create
> executables.
>
>
> Sauriez vous d'ou viens le pb?? c'est assez urgent....
> Un truc bizarre qui peut vous mettre sur la voie, est lorsque j ai
> dezipp0 le fichier .tar.gz, il n a pas mis les fichier dans
> /usr/src/pgsql/postgresql-6.4.2
> et non comme il est precis0 dans la doc dans
> /usr/src/pgsql
>
> Merci de votre aide
>
> Sandrine
> >
> Computers are like air conditioners...
> they stop working properly once you open Windows..!
> _________________________________________________________
> +TES-VOUS YAHOO!?
> Votre e-mail @yahoo.fr gratuit sur http://courrier.yahoo.fr
>
>
Computers are like air conditioners...
they stop working properly once you open Windows..!
_________________________________________________________
+TES-VOUS YAHOO!?
Votre e-mail @yahoo.fr gratuit sur http://courrier.yahoo.fr
- ------------------------------
Date: Thu, 11 Feb 1999 17:29:31 +0000
From: Clark Evans <clark.evans@manhattanproject.com>
Subject: Off-Topic, but Important [Fwd: Free Speech 0 ; US West 1]
Sorry to inntterupt your regularly scheduled programming,
but I think that this is important to everyone.
Best,
Clark
- - -----------------------
For Immediate Release
February 8, 1999
FINAL SCORE: FREE SPEECH-0, U S WEST-1
Cottonwood Communications and Rick Dahlgren were found to be in
civil contempt by a Federal Judge in Omaha, Nebraska for releasing
public documents to the Federal Communications Commission (FCC).
That's right, PUBLIC documents.
In an Order entered February 5, 1999, United States District
Judge Thomas M. Shanahan granted the "Amended Motion for
Order of Contempt" sought by U S West against Dahlgren and
Cottonwood. In the Judge's Order, he relied on a "Report and
Recommendation" from Federal Magistrate Judge Kathleen A. Jaudzemis
that clearly and unambiguously stated that the documents Dahlgren
and Cottonwood submitted to the FCC were "publicly available."
The Order was issued over objections filed by Dahlgren and
Cottonwood that strongly asserted that publicly available
documents cannot be afforded any protection and that U S West
forfeited it's protection by failing to meet the provisions of
the original Protective Order covering the documents in civil
litigation in Omaha, Nebraska.
"We're trying like the dickens to find the page in pgsql-general@postgreSQL.orgthe
Constitution that gives the court the authority to do this" said Rick
Dahlgren, Vice President, Cottonwood Communications.
U S West is seeking reimbursement of costs for prosecuting
the instant motion, for its costs before the FCC resulting from
Cottonwood's "wrongful disclosure," and for costs associated
with retrieving the documents in question. Further, the
Magistrate Judge recommends Dahlgren and java-os-project@spin.deCottonwood post a bond.
"We originally sued U S West for having put two businesses I own
out of business with inadequate telephone service. Now it
would appear that the Federal Court in Omaha is prepared to
assess fines against both my new company and me personally,
which if excessive enough, could put Cottonwood Communications
out of business. Since the Order is against me personally,
as well, maybe this time U S West can take my house" said
Dahlgren, who went on to say "Cottonwood Communications and
I will never willingly pay a single cent to anyone for
exerting our right to free speech under the Constitution
of the United States."
The documents in question were filed at the FCC regarding
Docket 98-147, and are also available to anyone who wishes to
see them at the Federal Courthouse in Omaha, Nebraska,
8:94CV89. "Unless, of course, you're me" said Dahlgren.
"In context, the documents show that when regulation provides
conditional entry to a market, U S West, under a cloak of
secrecy, does everything in its power to unfairly provide
itself and its partners essential control of the market
at the exclusion of all others" said Dahlgren.
For more information, contact:
Rick Dahlgren
Phone: (402) 896-2303
FAX: (402) 896-0268
e-mail: rd@cottonwood
- - -------- Original Message --------
Subject: Cottonwood in Civil Contempt for filing public documents in FCC proceeding
Date: Thu, 11 Feb 1999 11:28:12 -0500
From: James Love <love@cptech.org>
Reply-To: love@cptech.org
To: Multiple recipients of list INFO-POLICY-NOTES <info-policy-notes@essential.org>
Rick Dahlgren from Cottonwood communications has been having a lot of
legal problems with US West, including a current dispute where Rick's
firm has been hit with a civil contempt citation for filing public
documents from a federal court case in a public FCC proceeding. As I
understand matters, the documents in question were once covered by a non
disclosure agreement in a federal antitrust suit, but were subsequently
entered into the court's public record, "without restriction."
Nonetheless, Rick and his firm have been told that even though the
documents are now public, he cannot legally distribute them, even in a
public FCC proceeding, since he has promised to keep them confidential.
I asked Rick if he could put the court decisions about the comptempt
proceeding on the web and he has at:
http://www.cottonwood.com/legal.html
The following is a quote from Judge Magistrate Kathleen Jaudzemas's
recommendation to hold Rick Dahlgren and Cottonwood in contempt:
<----------begin excerpt --------------------------->
The protective order in question was intended to facilitate discovery by
forbidding the parties to use confidential information in other
proceedings absent consent or permission by the court. I emphasize that
plaintiffs would not have been given access to the information in
question but for the entry of the protective order. This court is
unaware of any contention that U S West somehow acted in bath faith in
designating its confidential information. The court is also unaware of
any motion or other effort made by the plaintiff corporations or the
Dahlgrens to amend the terms of the protective order. The protective
order certainly allows the plaintiffs' corporate officers to review the
portions of the court file that were not sealed. Members of the general
public may also review the court file if they have any interest in doing
so. The average member of the general public, however, probably does not
have the desire or incentive to peruse thousands of pages of court files
for secret documents. In contrast, plaintiffs knew of the existence and
location of U S West's confidential documents, had recently lost their
lawsuit against U S West, and apparently wished to place U S West in bad
light before the FCC (Footnote 3).
Evaluating plaintiffs' actions in light of the terms of the protective
order, I find that Cottonwood, through its agent Richard Dahlgren,
violated the court's order by intentionally delivering U S West's
confidential documents to the FCC.
<-------------end excerpt --------------------------->
Cottonwood, a small business, has been ordered to pay US West's legal
fees in this case.
jamie
- - --
James Love, Consumer Project on Technology
P.O. Box 19367, Washington, DC 20036
202.387.8030; f 202.234.5176
http://www.cptech.org, mailto:love@cptech.org
- ------------------------------
Date: Thu, 11 Feb 1999 13:11:46 -0500
From: David RR Webber <Gnosis_@compuserve.com>
Subject: Lawyers a go go.
Message text written by Clark Evans
>
Sorry to inntterupt your regularly scheduled programming,
but I think that this is important to everyone.
<<<
Sounds like its time for messrs Cottonwood and Co to cut
loose their tackle and get some new line. The judge doesn't
like them and the lawyers have got them in a nasty tangle.
I'd quit while I was behind on that battle and pick a new war
with a battle field of my own choosing. (Agree to pay
over a 99 year period - borrow the money from Nebraska
State and pay them back at a nickel a week! Got to be
cheaper for them than sending you to jail....).
On the broader front - it does show that within the XML/EDI
context it is very important to ensure that the information you
are sending is secure and only available to the party or
parties that you intend.
For instance what may appear to be innocent information
can suddenly become important. Say President Clintons
orders of flowers from 800flowers.com may be of interest
in certain quarters. Clearly the paranoid
would want to disclose a document not on easily copied
and manipulated content. If doing digital data you clearly
want to have the thing encrypted.
If you really want to be safe avoid digital data at all costs.
My favourite is writing things on to a piece of stair bannister
round dowelling with a yellow pen. Its a perfectly legal document.
Humans can read this, but photocopiers, fax machine
and scanners cannot! Don't forget to add 'do not transcribe
or type content into any electronic media' to be really safe.
It also does not fit neatly into cardboard boxes real well, or filing
cabinets.
The final solution is possibly a little extreme - create a new
country - and then export all lawyers there. The Brit's tried
this with Australia, but somehow something went awry
somewhere along the line.
DW.
- ------------------------------
Date: Thu, 11 Feb 1999 13:17:59 -0500 (EST)
From: Mark Wilson <mwilson@sundog.larc.nasa.gov>
Subject: no swap space
Hello,
I have a large data set stored using version 6.4.2 on a Sun Ultra 30
(Solaris 2.6 - 384MB RAM). While trying to preform a somewhat
complex select on one of the larger tables from the psql> command
promplt, I am given the following error message then dumped out out psql:
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
We have lost the connection to the backend, so further processing is
impossible. Terminating.
If I try the same query from a cgi script written in perl, the script
comes back empty and this warningappears on my console screen:
WARNING: Sorry, no swap space to grow stack for pid 15195 (postgres)
The swap space on the system I'm using looks to be around 275MB and
it remains at about 1% capacity during the operation that bombed.
I've looked around the mail archives and have not found any similar
problems or solutions. Does anyone have any ideas? Thanks!
- - -Mark.
- - --- fax: (757)825-8659
Mark Wilson voice: (757)827-4631
Analytical Services & Materials, Inc. email: m.r.wilson@larc.nasa.gov
- ------------------------------
Date: Thu, 11 Feb 1999 19:32:02 +0100
From: Gilles Darold <darold@neptune.fr>
Subject: Re: [GENERAL] Installer PostGres..
Bonjour Sandrine,
Ton probleme semble venir du fait que tu n'a pas installer le compilateur
C++ sur ta machine.
Ca n'a rien a voir avec le path, mais il est preferable aussi que tu renomme
le repertoire
/usr/src/pgsql/postgresql-6.4.2 en /usr/src/pgsql car la plupart des path
par defaut pointent
sur ce nom (a moins que le configure ne s'en occupe).
Donc soit installer le C++ sur ta machine, soit si je me rappelle bien je
crois que postgresql
n'a pas besoin du compilo C++, dans ce cas il faut oublier le ./configure et
mettre en
commentaire les lignes relatives au Flag C++. Si tu prend les paths par
defaut, il suffit
de lancer les commandes make qui vont bien. La franchement je suis pas sur,
je vais regarder
ce soir.
Pour qu'on puisse t'aider, il faut que tu nous dise la version et le type de
systeme que tu
utilise pour etre sur d'aller au plus precis. Je crois aussi le mieux c'est
de s'exprimer en anglais
sur cette mailing liste car je n'ai encore jamais vu d'article en francais
:-)
Bien, si tu n'y arrive pas, envoi moi un mail demain a mon adresse, je
pourrais t'aider en
ligne dans l'apres-midi...
Bonne soiree et bon debut sur PostgreSQL
A+, Regards
Gilles
Note : pour detarer un fichier (si tu est sous linux) il y a une commande
plus simple :
tar xzvf postgresql-6.4.2.tar.gz (c'est l'option z qui s'occupe
du gunzip) !
- ------------------------------
Date: Thu, 11 Feb 1999 18:45:42 +0000
From: Stuart Rison <stuart@ludwig.ucl.ac.uk>
Subject: Re: [GENERAL] Installer PostGres..
>Pour qu'on puisse t'aider, il faut que tu nous dise la version et le type de
>systeme que tu
>utilise pour etre sur d'aller au plus precis. Je crois aussi le mieux c'est
>de s'exprimer en anglais
>sur cette mailing liste car je n'ai encore jamais vu d'article en francais
>:-)
>
Moi non plus mais maintenant ca fait trois (et presque une habitude) ;)
amicalement,
S.
+-------------------------+--------------------------------------+
| Stuart Rison | Ludwig Institute for Cancer Research |
+-------------------------+ 91 Riding House Street |
| Tel. (0171) 878 4041 | London, W1P 8BT, UNITED KINGDOM. |
| Fax. (0171) 878 4040 | stuart@ludwig.ucl.ac.uk |
+-------------------------+--------------------------------------+
- ------------------------------
Date: Thu, 11 Feb 1999 18:57:45 +0000
From: Martin Young <myoung@bristol.st.com>
Subject: Re: Lawyers a go go.
> The final solution is possibly a little extreme - create a new
> country - and then export all lawyers there. The Brit's tried
> this with Australia, but somehow something went awry
> somewhere along the line.
Hrm. The whole of Europe did that with America and it seems to have been
moderately successful.
- - --
Martin Young, at STMicroelectronics, \O O \O O
at 1000 Aztec West, Almondsbury, //\ /\\ //\ /\\ ,^O
Bristol, BS32 4SQ. +44 145 461 1523 / | / \ / | // // ` \\__|O
myoung@bristol.st.com Ah Ah Ah Ah Stayin' alive
- ------------------------------
Date: Thu, 11 Feb 1999 19:06:43 +0000
From: Paulo da Silva <pdasilva@esoterica.pt>
Subject: Conditioned access to a database
Hello,
I'm evaluating sql/postgresql for the following purpose:
I need to have a database with lots of "records".
I need to allow groups of users to access sets of
those records grouped by the contents of one field.
For example, the group A can only access records that
have the dptm field
If the subject is not simple, pls just tell me
which doc to read.
TIA
Paulo
- - --
"Esta Ilha pequena que habitamos"
Luis de Camoes
(International version soon available)
Paulo (pdasilva@esoterica.pt)
- ------------------------------
Date: Thu, 11 Feb 1999 14:46:19 -0600 (CST)
From: Kevin Heflin <kheflin@shreve.net>
Subject: need help separating a field
I have a table with a field of 'username_password' where the data is in
the format of:
username/password
what I would really like to do, is create a new field of 'username' and
another of 'password' and with some magic SQL statement select all from
username_password, and spit up the pair, and insert them back into the
newly created 'username' and 'password' fields.
Is this even possible? and if so, would anyone be willing to give me a
hint?
Kevin
- - --------------------------------------------------------------------
Kevin Heflin | ShreveNet, Inc. | Ph:318.222.2638 x103
VP/Mac Tech | 333 Texas St #619 | FAX:318.221.6612
kheflin@shreve.net | Shreveport, LA 71101 | http://www.shreve.net
- - --------------------------------------------------------------------
- ------------------------------
Date: Thu, 11 Feb 1999 15:05:21 -0600
From: "Ross J. Reedstrom" <reedstrm@rice.edu>
Subject: Re: [GENERAL] need help separating a field
Well, I once split up a bunch of multiline addresses with lines like
this:
select "PerIndex",substr("addr",1,(strpos("addr",'\n')- 1)) as addr,
substr("addr",(str
pos("addr",'\n')+1)) as addr2 into tmp2_addr from tmp_addr;
so, try something like (untested):
select substr(username_password,1,(strpos(username_password,'/')-1)) as
username, substr(username_password,(strpos(username_password,'/')+1)) as
password into new_table from table;
Kevin Heflin wrote:
>
> I have a table with a field of 'username_password' where the data is in
> the format of:
>
> username/password
>
> what I would really like to do, is create a new field of 'username' and
> another of 'password' and with some magic SQL statement select all from
> username_password, and spit up the pair, and insert them back into the
> newly created 'username' and 'password' fields.
>
> Is this even possible? and if so, would anyone be willing to give me a
> hint?
>
> Kevin
>
> --------------------------------------------------------------------
> Kevin Heflin | ShreveNet, Inc. | Ph:318.222.2638 x103
> VP/Mac Tech | 333 Texas St #619 | FAX:318.221.6612
> kheflin@shreve.net | Shreveport, LA 71101 | http://www.shreve.net
> --------------------------------------------------------------------
- - --
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005
- ------------------------------
Date: Thu, 11 Feb 1999 16:08:12 -0500 (EST)
From: Stephan Doliov <statsol@statsol.com>
Subject: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
> Since we are tossing ideas around, here is my two cents.
> .1c In order not to worry about royalties we can donate proceeds to
> PostgreSQL.
Amen/Bravo! This would truly be in the spirit of PostgreSQL
Regarding the books contents. I think
I. Section 1 - Intro
1. Brief Overview History
2. Getting and Installing
3. Setting up a Database
4. Maintaining a Database
II. Section II - Making it work
1. Postgres' type system
2. Triggers & Functions
3. Embedded Scripting Languages
a) pl/pgsql
etc.
4. External access to postgres
a) libpq
b) libpq++
c) odbc
etc.
5. Interfacing PostgreSQL to the Web
a) perl
b) php3
c) pygreSQL
others
III. Reference and Tekkie Stuff
1. The built-in functions
2. Query Optimization
3. Postmaster tuning & performance issues
IV. New Features
This would be a section where people could insert information related to
the latest release. Much like law reports have addenda inserts at the
back.
my $0.02
steve doliov
- ------------------------------
Date: Thu, 11 Feb 1999 15:48:14 +0100
From: TSchoessow@t-online.de (Thomas Schoessow)
Subject: unsubscribe
unsubscribe
- - ----------------------------------------------------------------------------
- - ------------------
E-Mail: TSchoessow@topmail.de http://www.tschoessow.de
Secure E-Mail: secure@tschoessow.de
Certified PGP Key ID 0x3062C4A1
ICQ 18107512
- - ----------------------------------------------------------------------------
- - -------------------
- ------------------------------
Date: Thu, 11 Feb 1999 14:28:12 -0800 (PST)
From: Jonathan Scott <jsscott@falcon-srv.csc.calpoly.edu>
Subject: Problems compiling
Hello fellow PostgreSQL users.:)
I am having trouble with the configure file for version 6.4.2. I have
installed and configured and compiled it before without this problem.
However this is a new machine with a wacked out debian install. Here is
the output from my configure run:
$ ./configure --prefix
loading cache ./config.cache
checking host system type... i586-pc-linux-gnu
checking echo setting...
checking setting template to... linux_i386
checking setting USE_LOCALE... disabled
checking setting CYR_RECODE... disabled
checking setting MULTIBYTE... disabled
checking setting DEF_PGPORT... 5432
checking setting USE_TCL... disabled
checking setting USE_PERL... disabled
checking setting USE_ODBC... disabled
checking setting ASSERT CHECKING... disabled
checking for gcc... gcc
checking whether the C compiler (gcc -O2 ) works... yes
checking whether the C compiler (gcc -O2 ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
- - - setting CPPFLAGS- - setting LDFLAGSchecking for c++... no
checking for g++... no
checking for gcc... gcc
checking whether the C++ compiler (gcc ) works... no
configure: error: installation or configuration problem: C++ compiler cannot create executables.
Any ideas? I cannot figure it out. Please help, this is for a senior
project I am working on and I cannot graduate if I dont get it done!:)
TIA,
Jonathan Scott
- ------------------------------
Date: Thu, 11 Feb 1999 19:33:06 -0200
From: "Ricardo J.C.Coelho" <pulsar@truenet-ce.com.br>
Subject: RES: [GENERAL] Conditioned access to a database
Ol Paulo,
Como falamos a mesma l°ngua, estou respondendo em Portuguns.
Veja o cap°tulo que fala sobre VIEWS e RULES. Vocn deve criar uma "view"
para cada grupo selecionando apenas os registros que vocn quer permitir o
acesso. Por exemplo:
create view TABELA_GRUPOA as select * from TABELA where dptm create view TABELA_GRUPOB as select * from TABELA where
dptm
Dar permissno de acesso para a "view" e nno para TABELA (Veja GRANT).
Execute a query: select * from TABELA_GRUPOA;
Como o Pgsql nno permite alterarno de "views", vocn deve criar "rules" nas
"views" para alterar TABELA, se for o caso.
Espero que tenha lhe ajudado.
Ricardo Coelho.
- - ----- Mensagem original -----
De: Paulo da Silva [SMTP:pdasilva@esoterica.pt]
Enviada em: Quinta-feira, 11 de Fevereiro de 1999 16:07
Para: pgsql-general@postgreSQL.org
Assunto: [GENERAL] Conditioned access to a database
Hello,
I'm evaluating sql/postgresql for the following purpose:
I need to have a database with lots of "records".
I need to allow groups of users to access sets of
those records grouped by the contents of one field.
For example, the group A can only access records that
have the dptm field
If the subject is not simple, pls just tell me
which doc to read.
TIA
Paulo
- - --
"Esta Ilha pequena que habitamos"
Luis de Camoes
(International version soon available)
Paulo (pdasilva@esoterica.pt)
- ------------------------------
End of pgsql-general-digest V1 #219
***********************************
------------------------------
End of pgsql-general-digest V1 #220
***********************************
pgsql-general by date: