Re: [SQL] feature request ?

es not put any problems to anyone, does it ? You check that the reference is set and then proceed to use it's value. Also you might consider giving it a rest and stop shouting in the forum - it's not your back yard you know. Peace, -- Radu-Adrian Popescu CSA, DBA,

Re: [SQL] feature request ?

" should account for that ?! You can think of values in plpgsql as wrapper objects that carry a value and have a "is_null" flag; I have no idea how they're implemented in PostgreSQL or in any RDMBS in general but this should do it, at least for a naive implementation.

Re: [SQL] Login information in system tables

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Doorduin wrote: | Hi, | | I was wondering if it is possible to query the sytem tables to get | an overview of user logins in psql. Check out the pg_user table. Regards, - -- Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. +40213212243

Re: [SQL] returning a recordset from PLpg/SQL

as OTHER, bind the parameter and get back a ResultSet. All fine and marry, but I can't figure out how to use _this_ form of the function from psql. I've read and tried the manual examples and they do work. However, I can't make this one work. Thanks in advance, -- Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. +40213212243 ---(end of broadcast)--- TIP 8: explain analyze is your friend

Re: [SQL] Catching DML exceptions in PL/pgSQL

pgSQL !!! :-O Cheers, -- Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Re: [SQL] Catching DML exceptions in PL/pgSQL

n 7.5 ? :-) Cheers, -- Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [SQL] Catching DML exceptions in PL/pgSQL

At 6/17/2003 11:44, Tomasz Myrta wrote: Dnia 2003-06-17 11:25, U¿ytkownik Radu-Adrian Popescu napisa³: Hello all, (and sorry if this has been aswered before) Take this piece of code for example: . begin _res.code:=1; select id into iid from log where id=_id; if

[SQL] Catching DML exceptions in PL/pgSQL

re the function always returns _res ? Something along the lines of Oracle's exception handling, or the @@error trick in mssql ? Regards, -- Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd.

Re: [SQL] insert rule doesn't see id field

I'm extremely sorry about the post in this thread ! Had a brain cramp, my appologies. Should have been Re: [SQL] SQL function parse error. Terribly sorry again ! = Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. - Original Message - From: "Radu-Adrian Popescu" &l

Re: [SQL] insert rule doesn't see id field

To everyone interested, check out Tom Lane's and Bruce's comments on pgsql-hackers: http://archives.postgresql.org/pgsql-hackers/2003-01/msg00446.php There seems to be some consensus towards removing $ from the list of allowed operator characters. Regards, = Radu-Adrian Popesc

Re: [SQL] SQL function parse error ?

we all want to see postgresql up there where it belongs. That being said, I do hope that superficial replies trying to prove me wrong will stop, as they actually don't help anyone. Regards, = Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. - Original Message ----- From: "R

Re: [SQL] SQL function parse error ?

Nice to see that things are starting to move. I was wandering however whether I've succeeded in making a point. Regards, = Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. - Original Message - From: "Tom Lane" <[EMAIL PROTECTED]> Subject: Re: [SQL] SQL

Re: [SQL] SQL function parse error ?

ELECT * is the same as SELECT *. I rest my case. Cheers, = Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. - Original Message - From: "Tom Lane" <[EMAIL PROTECTED]> To: "Achilleus Mantzios" <[EMAIL PROTECTED]> Cc: "Radu-Adrian Popescu" <

Re: [SQL] SQL function parse error ?

then have a [very suble] bug. Simply put, operator precedence over local identifiers/parameters, which i belive is a de facto standard in most languages (no flames please !) :) Cheers, ===== Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. - Original Message - From: "Achilleus

Re: [SQL] SQL function parse error ?

onstructive, not slaping eachother. For that reason, i appologize for whatever harsh remarks i've made, and simply hope to get a straight answer or even better a conversation. Regards, = Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. - Original Message - From: "Tom Lane"

Re: [SQL] SQL function parse error ?

p clear this issue. Cheers, = Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. - Original Message - From: "Tomasz Myrta" <[EMAIL PROTECTED]> To: "Radu-Adrian Popescu" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, January 09, 2003 3:22

Re: [SQL] SQL function parse error ?

thing from Mysql to Oracle will get quite annoyed on this one. Hope the people in charge of the parser will get to the bottom of this... ... and please forgive my caustic tone. = Radu-Adrian Popescu CSA, DBA, Developer Aldratech Ltd. - Original Message - From: "Tomasz Myrta"

[SQL] SQL function parse error ?

Hello !   There is a strange behaviour in the SQL function parser (haven't tested this with the plpgsql lang) when using standard operators and function parameters.   Take the following for example: create or replace function testfunc1(int) returns setof test as'    select * from test where

Re: [SQL] PostgreSQL X Resin EE

I have sucessfuly used resin (standard, not EE, with datasource, pooling) and postgresql. =Radu-Adrian PopescuCSA, DBA, DeveloperAldratech Ltd. - Original Message - From: Pedro Igor To: [EMAIL PROTECTED] Sent: Thursday, January 02, 2003 3:16 PM Subject: [SQL]

Re: [SQL] How to use BYTEA type?

out after reading your email. If some of the postgresql guys could point the location of the documentation of undocumented functions :-) that'd be great. Radu-Adrian Popescu DBA/programmer at www.aldratech.com Christopher Sawtell wrote: >Greetings folks, > > Please could a kind