> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Joris
> Sent: 08 May 2005 19:31
> To: pgsql-bugs@postgresql.org
> Subject: [BUGS] BUG #1654: can't run SQL commands
>
>
> The following bug has been logged online:
>
> Bug reference: 1654
> L
An issue came up on irc. How come that this work:
SELECT generate_series(0,1);
but
SELECT foo(0,1);
does not, where foo is my own set returning function, like this example:
CREATE FUNCTION foo(a int, b int)
RETURNS setof int
AS 'BEGIN RETURN NEXT a;
On Mon, 9 May 2005, Dennis Bjorklund wrote:
> [ I can call sql or C SRFs without FROM, but not plpgsql.]
Trying this in pltcl (while knowing nothing about tcl and the docs not
mentioning any srf support) shows:
CREATE FUNCTION tclset() RETURNS SETOF int AS 'return 0' LANGUAGE pltcl;
SELECT *
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> So it seems that it's not just the type that decide how the function can
> be used, it's also the language the function is defined in.
Yup.
> Bug?
Unimplemented feature.
regards, tom lane
---(end of
On Mon, 9 May 2005, Tom Lane wrote:
> > Bug?
>
> Unimplemented feature.
Is
SELECT 42, srf();
the same as
SELECT 42, * FROM srf();
?
In my view the first version is an error. It's not like you can put a
normal table in the select list, so why can we put a set returning
function there?
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> Is
>SELECT 42, srf();
> the same as
>SELECT 42, * FROM srf();
> ?
No.
> In my view the first version is an error. It's not like you can put a
> normal table in the select list, so why can we put a set returning
> function there? Ie, is it rea
it is about null problem
declare
res numeric(15,2);
_pida integer[4]; < Problem is here must be ---> pida
integer[4]='{}';
_pid integer;
_rec record;
..
"ALÝ ÇELÝK" <[EMAIL PROTECTED]>, haber iletisinde þunlarý
yazdý:[EMAIL PROTECTED]
>
> I have a
The following bug has been logged online:
Bug reference: 1655
Logged by: Emanuel Brokmann
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Red Hat Linux 3.2.3-42
Description:trapping errors doesn't work
Details:
while executing:
>>BEGIN
>>
"Emanuel Brokmann" <[EMAIL PROTECTED]> writes:
> while executing:
> >>BEGIN
> >> insert into comlineprintboxen VALUES(109, '', '', '', >>'', '');
> >>EXCEPTION
> >> WHEN unique_violation then
> >>UPDATE comlineprintboxen SET verteiler='', >>panel='', dose='',
> switch='', port='' WHERE >>pri
