I just find a workaround, which also may shed light on the bug itself:
select 'hello ' || coalesce('there','there',0::text);
?column?
-
hello there
(1 row)
And this is very strange indeed:
select 'hello ' || coalesce('there','there',0);
?column?
-
hello 13635
select 'hello ' || coalesce('there','there');
ERROR: Function 'text(unknown)' does not exist
Unable to identify a function that satisfies the given argument
types
You may need to add explicit typecasts
It seems clear that the coalesce construction must return a string - so why
do
Hi!
I'm found that call function has bug:
some function have more than one arguments and
if one argument is NULL, then all other arguments
is NULL too! But function calling only with one
NULL arguments. Why?!
My system Linux Slackware 7.0, Postgres 7.0.2.
kernel 2.2.16
log file attached.
Dmit
[EMAIL PROTECTED] writes:
> psql:triggertest.sql:4: NOTICE: plpgsql: ERROR during compile of c_fnc
> near line 1
> "sql:triggertest.sql:4: ERROR: parse error at or near "
Sounds like you saved your file with DOS-style newlines (\r\n). The
plpgsql parser doesn't think \r is whitespace. That'
Roland Szabo ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Special character pervents psql from parsing?
Long Description
Consider the two expressions in the example code. They are almost the same, the only
difference is, th
Roland Szabo ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Fails to add function from file with \i in psql
Long Description
For maintainance reasons, sql statements for our databases are saved in files, and
upon installation
[EMAIL PROTECTED] writes:
> CREATE TABLE ninhada (
> c_id_mae int,
> n_id int,
> c_id_pai int,
> n_dta_nasc date,
> PRIMARY KEY (n_id, c_id_mae),
> FOREIGN KEY (c_id_mae) REFERENCES caes (c_id)
>ON DELETE CASCADE,
> FOREIGN KEY (c_id_pai) REFERENCES caes (c_id)
Pedro Alves ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
CHECK evaluation error when using more than one table
Long Description
Creating a table with the code shown, everytime I try to insert values I get the same
"ERROR: E