Troels Arvin <[EMAIL PROTECTED]> writes:
> On Sat, 27 Nov 2004 14:24:40 +, Andrew - Supernews wrote:
>> something is assuming that constraint_name is unique within the schema,
>> which of course is not the case in the above example.
> The problem makes the INFORMATION_SCHEMA rather useless for
Neil Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> There is no ELSEIF construct.
> Sure, but it would be nice to throw a syntax error rather than silently
> accepting the function. Unfortunately the way PL/PgSQL's parser works
> doesn't make this very easy.
Actually, the simplest solu
Neil Conway <[EMAIL PROTECTED]> writes:
>> (BTW, another thing this example exposes is that we don't issue warnings
>> about trivially-dead-code, such as statements in a basic block that
>> follow a RETURN. This would probably be also worth doing.)
> Attached is a patch that implements this. Spe
Hello:
Sorry for my english, i am install
the 8.0 beta5 version for Windows, all ok, but
when igniting the equipment for the second time, it
appears to me the legend:
"could not receive server response to SSL
negotiation pocket"
nevertheless postmaster this running.
excuse by the annoy
Hi,
I downloaded pgSQL 8.0 beta 5 just yesterday. After installing the service
did't start so I tried to run it manually and I recieved message that the
service was started and had been instantly stopped because of inactivity.
I was also experiencing some more difficulties while I was trying
Hi all.
Your windows installer of PostgreSQL 8.0.0 Beta 5
(postgresql-8.0.0-beta5-en.msi) is probably corupted. Nothing's happend,
when I try execute it. When I open it by WinRar, there are unreadable
symbols instead some file and folder names. I have try older versions
(beta 4) too with the sa
On Sat, 27 Nov 2004 14:24:40 +, Andrew - Supernews wrote:
> A similar issue may exist with the check_constraints view, which was the
> only other place I found where constraint_name is used without any table
> name being present. I don't know what the spec says, but it seems that
> something i
Found this in 7.4.5, verified it's still in 8.0b4:
test=> select * from information_schema.referential_constraints;
test|public|$1|test|public|reftest1_pkey|NONE|NO ACTION|CASCADE
test|public|$1|test|public|reftest1_pkey|NONE|NO ACTION|NO ACTION
test|public|$1|test|public|reftest1_pkey|NONE|NO ACT
Neil Conway wrote:
(BTW, another thing this example exposes is that we don't issue warnings
about trivially-dead-code, such as statements in a basic block that
follow a RETURN. This would probably be also worth doing.)
Attached is a patch that implements this. Specifically, if there are any
stat
Hi,
I was installing a brand new PostgreSQL 7.4.6 on FreeBSD 4.10 using ports:
portinstall postgresql7
portinstall postgresql-pltcl
portinstall p5-postgresql-plperl
but when I was going to install the plperl, I've found following error:
Nov 27 11:06:51 biblio postgres[93190]: [1-1] ERROR: could no
10 matches
Mail list logo
