Hello,
I'm trying to use the ROWTYPE return value of a plpgsql function in a
SELECT query. The test code is below.
The following query is accepted:
select id, usr, code, line1, line2 from tbl, get_lines(1);
idusr code line1 line2
--
1 one 1
Lars Erik Thorsplass wrote:
On Tue, 20 Jul 2004 09:45:06 -0600, Scott Marlowe [EMAIL PROTECTED] wrote:
Kinda like this:
SELECT *, acl_check( objects.obid, user_id ) AS mode FROM objects
WHERE mode 0;
Here's the problem. In order to do the select, the query first needs to
run
Is there a sleep function of some kind? I wanted to simulate a query
taking a long time to execute for testing purposes.
Thanks,
John DeSoi, Ph.D.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
John DeSoi wrote:
Is there a sleep function of some kind? I wanted to simulate a query
taking a long time to execute for testing purposes.
I can't think of one, no. I think you will have to use one of the
server-side languages and call a sleep in there.
--
Bruce Momjian
Philippe Lang wrote:
But the same query with a parameter returns an error:
select id, usr, code, line1, line2 from tbl, get_lines(code);
-- ERROR: function expression in FROM may not refer to other relations
of same query level
This is as expected and required -- you cannot refer to other FROM
Title: ERROR: Cross-database references are not implemented
How do I explicidly create a cross-database reference?
Mind you these databases are on the same server.
In MSSQL you could do that through enterprise manager.
Any help would be appreciated.
Theo Galanakis wrote:
How do I explicidly create a cross-database reference?
Mind you these databases are on the same server.
In MSSQL you could do that through enterprise manager.
Any help would be appreciated.
You cannot do cross database references per se, but you can use schemas,
which
Folks,
I'm seeing this bizarre, unreproducable error in my logs:
[2] Wrong datatype for second argument in call to in_array
SQL: SELECT sf_event_decendants(66645,111)
The problem is that it's proven completely impossible to reproduce this error
at test time; it only seems to happen in
