Steve,
Hmmm ... I'm using PostgreSQL for quite a few contortions of data, and
I can't say that I've encountered anything quite like the problems
you're having. It may be that you actually have a compile problem with
Postgres rather than a SQL problem.
Hi,
Apologies for re-posting - this problem is giving me a bit of a
headache.
Basically, my problem is that in a number of (to me surprising) contexts
an explicit cast from a string literal to some character data type is
required by PostgreSQL, where such casts are not required by other rdbms
w
Christophe Labouisse <[EMAIL PROTECTED]> writes:
> I'm trying to run pg_dumpall to backup all my users' bases but since I
> have configure pg_hba.conf to "passwd" pg_dumpall always fails:
pg_dumpall doesn't work very well with password authentication (and
even if it did, storing the password in a
I'm trying to run pg_dumpall to backup all my users' bases but since I
have configure pg_hba.conf to "passwd" pg_dumpall always fails:
su-2.03$ pg_dumpall >backup.dat # I'm the postgres unix user.
Password: psql: Password authentication failed for user 'postgres'
Password: psql: Password authenti
Micheal,
Thanks, I was thinking that something like this should work.
However, I am having a problem with it. here is what I am doing.
begin;
INSERT INTO table (serial_col) (SELECT nextval('seq_serial_col'));
commit;
first I needed to add parens around the select statement. The
results are n
From: "Picard, Cyril" <[EMAIL PROTECTED]>
> Thank you ! I planned to use the 7.1 to get the outer join capability.
>
> Is the 7.1 stable ?
Pretty much - it's reached release candidate stage and I've been using it
for development for a while now.
- Richard Huxton
---(en
Thank you ! I planned to use the 7.1 to get the outer join capability.
Is the 7.1 stable ?
> -Message d'origine-
> De: Richard Huxton [SMTP:[EMAIL PROTECTED]]
> Date: mardi 3 avril 2001 10:06
> À:Picard, Cyril; [EMAIL PROTECTED]
> Objet:Re: [SQL] passing null parameter to
From: "Picard, Cyril" <[EMAIL PROTECTED]>
> Hello
> I wrote a plpgsql function with few parameters ; when I call the function,
> some of the parameters can be null.
> In this case, all the parameters are considered as null in the function's
> body ! is it a feature ? how can I work around this ?
From: "Gerald Gutierrez" <[EMAIL PROTECTED]>
>
> I've been looking into indices and which ones to create and I'm getting
> myself a little confused. The "PostgreSQL Introduction and Concepts" book
> didn't help very much. I wonder if a kind soul can give me some tips.
>
> SELECT * FROM T1 WHERE a
