Re: [HACKERS] Is current_user a function ?

2002-11-29 Thread Masaru Sugawara
ould work in 7.3 too. I now understand it doesn't work any more -- as well, session_user(), user(), current_date(), current_time(), current_timestamp() and etc. Thank you, Rod and Tom. Regards, Masaru Sugawara ---(end of broadcast)---

[HACKERS] Is current_user a function ?

2002-11-28 Thread Masaru Sugawara
near "(" at character 20 Regards, Masaru Sugawara renew=# \df List of functions Result data type | Schema |

Re: quote_ident and schemas (was Re: [HACKERS] connectby with schema)

2002-11-23 Thread Masaru Sugawara
becoming a reserved word. > > If it's not too late, I'd like this to get into 7.3, but in any case, please > apply to HEAD. > Thank you for your quick job. Regards, Masaru Sugawara - CREATE SCHEMA ms; CREATE TABLE ms.test (id int4, pare

[HACKERS] connectby with schema

2002-11-22 Thread Masaru Sugawara
, 'id', 'parent_id', '101', 0, '.') as t(id int4, parent_id int4, level int, branch text); ERROR: Relation "ms.test" does not exist Regards, Masaru Sugawara ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [HACKERS] Transactions through dblink_exec()

2002-10-13 Thread Masaru Sugawara
On Sat, 12 Oct 2002 23:37:18 -0700 Joe Conway <[EMAIL PROTECTED]> wrote: > Masaru Sugawara wrote: > > I'm hoping that dblink_exec() returns something like warning if those > > who intend to do transactions make a declaration of > > blink_exec('dbname=som

[HACKERS] Transactions through dblink_exec()

2002-10-12 Thread Masaru Sugawara
e', 'BEGIN; some queries; COMMIT/ROLLBACK/END;') or use dblink_exec('BEGIN/COMMIT/ROLLBACK/END') around dblink_exec('some queries')s. If not, your transactions won't work. Regards, Masaru Sugawara > On Fri, 27 Sep 2002 09:35:48 -0700 > Joe Conway <

Re: [HACKERS] Does setof record in plpgsql work well in 7.3?

2002-09-29 Thread Masaru Sugawara
END LOOP; RETURN NEXT rec3; RETURN; END; ' LANGUAGE 'plpgsql'; SELECT * FROM myfunc(1) AS t(a integer, b text); a | b ---+ 1 | test 5 | function1 1 | test 5 | function11 1 | test (5 rows) Regards, Masaru Sugawara

[HACKERS] Does setof record in plpgsql work well in 7.3?

2002-09-29 Thread Masaru Sugawara
rd AS ' SELECT * FROM test WHERE a = $1; ' LANGUAGE 'sql'; SELECT * FROM myfunc(1) AS t(a integer, b text); a | b ---+ 1 | function1 1 | function11 (2 rows) Regards, Masaru Sugawara ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] About connectby() again

2002-09-27 Thread Masaru Sugawara
On Thu, 26 Sep 2002 16:32:08 -0700 Joe Conway <[EMAIL PROTECTED]> wrote: > Masaru Sugawara wrote: > > The previous patch fixed an infinite recursion bug in > > contrib/tablefunc/tablefunc.c:connectby. But, other unmanageable error > > seems to occur even if a tabl

Re: [HACKERS] About connectby() again

2002-09-26 Thread Masaru Sugawara
INTO connectby_tree VALUES(10,11); > INSERT INTO connectby_tree VALUES(111,11); > INSERT INTO connectby_tree VALUES(1,111); > > SELECT * FROM connectby('connectby_tree', 'keyid', 'parent_keyid', '11', 0, '-')

[HACKERS] About connectby() again

2002-09-26 Thread Masaru Sugawara
VALUES(1,111); SELECT * FROM connectby('connectby_tree', 'keyid', 'parent_keyid', '11', 0, '-') AS t(keyid int, parent_keyid int, level int, branch text) ERROR: infinite recursion detected Regards, Masaru Sugawara --

Re: [HACKERS] About connectby()

2002-09-08 Thread Masaru Sugawara
9 |5 | 2 | 2~5~9 > 10 |9 | 3 | 2~5~9~10 > 11 | 10 | 4 | 2~5~9~10~11 > (8 rows) > > Thanks for the feedback! > > Joe > > Regards, Masaru Sugawara ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[HACKERS] About connectby()

2002-09-07 Thread Masaru Sugawara
INTO connectby_tree VALUES(9,11);<-- infinite Regards, Masaru Sugawara ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org