On Fri, 10 Sep 1999, Tom Lane wrote:
> Stuart Rison <[EMAIL PROTECTED]> writes:
> > Now this would work except that there's a problem with pl/pgSQL such that
> > when you pass several values to a plpgsql function and one of them is
> > NULL, then all values passed to the function become NULL.
>
Jeff, Bryan, Teodor:
thank you all so much!!!
one related/furthur question:
>0. LOCK TABLE IN EXCLUSIVE MODE
this is what I'm concerned. Now, the "shutdown" a table gracefully
is solved. How about the whole postmaster (in some other situation),
how can I shut it down GRACEFULLY (i.e., I know tha
>
> On Tue, 14 Sep 1999, you wrote:
> > I have a table with and email address and a datetime timestamp. What
> > would be the easiest way to select the 3 earliest timestamps (earliest
> > being furthest in the past from the current date)
>
> lots of ways =) though the first that comes to mind i
On Tue, 14 Sep 1999, you wrote:
> I have a table with and email address and a datetime timestamp. What
> would be the easiest way to select the 3 earliest timestamps (earliest
> being furthest in the past from the current date)
lots of ways =) though the first that comes to mind is the use of cu
Hi,
Each time I try to insert an ascii file with the
COPY FROM command, I get the following message:
"ERROR: COPY command, running in
backend with effective uid 501 (that's Postgres), could not open file
'/usr/local/.../cltclr001' for reading. Error: Permission not allowed
(13)."
Wha
Hi,
The UNIQUE constraint doesn't work on a field if
I use a DEFAULT clause on a table.
The following table works with UNIQUE
constraint:
create table cltclt001(
tcid int2,
tcnom text unique
);
but this one accept several same tcnom
value:
create table cltclt001(
tcid int2 de
I have a table with and email address and a datetime timestamp. What
would be the easiest way to select the 3 earliest timestamps (earliest
being furthest in the past from the current date)
amy cheng wrote:
>
> hi, all experts there, greetings!
>
> Just minutes ago, my boss found out one of the attributes in a
> table is too short (varchar 64 for url), we need to make
> it wider to 85 A.S.A.P. Seems that alter table can not do it.
> So, I used pg_dump, (how to do it gracefully?) im
> hi, all experts there, greetings!
>
> Just minutes ago, my boss found out one of the attributes in a
> table is too short (varchar 64 for url), we need to make
> it wider to 85 A.S.A.P. Seems that alter table can not do it.
> So, I used pg_dump, (how to do it gracefully?) immediately drop the ta
hi, all experts there, greetings!
Just minutes ago, my boss found out one of the attributes in a
table is too short (varchar 64 for url), we need to make
it wider to 85 A.S.A.P. Seems that alter table can not do it.
So, I used pg_dump, (how to do it gracefully?) immediately drop the table,
shutd
>We still don't know if Postgresql can do it, do we?
no, we do not know ;-)
anybody there please?
amy
__
Get Your Private, Free Email at http://www.hotmail.com
On Fri, 10 Sep 1999, omid omoomi wrote:
> hi evey body,
> I've some comments :
> 1) I believe that there are some problems in table and db design and you are
> doing the job in its hard way! There seems to be no primarry key defined on
> the table. you can compose it at the end of your DDL(crea
12 matches
Mail list logo
