Jason Best wrote:
> 1.6.3
Yeah, that code has changed a lot since then. Can you try 1.8b5 please?
Thanks, Dave.
---(end of broadcast)---
TIP 6: explain analyze is your friend
Jason Best wrote:
> It seems to be fixed in 1.8b5. Thanks.
Great, thanks for testing.
Regards, Dave.
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's
@postgresql.org
Subject: Re: [pgadmin-support] Double Quotes
Jason Best wrote:
> 1.6.3
Yeah, that code has changed a lot since then. Can you try 1.8b5 please?
Thanks, Dave.
---(end of broadcast)---
TIP 4: Have you searched our list archi
: [pgadmin-support] Double Quotes
Jason Best wrote:
> Hi,
>
> I think I have come across a bug. I am trying to
create
> a new stored proc using plperl. I have an IN variable declared as a
> table called XmlData. The SQL being generated is wrong:
What version of pgAdmin? It
Jason Best wrote:
> Hi,
>
> I think I have come across a bug. I am trying to create
> a new stored proc using plperl. I have an IN variable declared as a
> table called XmlData. The SQL being generated is wrong:
What version of pgAdmin? It works for me on 1.8.0 beta 5.
Regards, D
Hi,
I think I have come across a bug. I am trying to create
a new stored proc using plperl. I have an IN variable declared as a
table called XmlData. The SQL being generated is wrong:
CREATE FUNCTION test.testsub2(IN xml test.""XmlData"", OUT id integer)
AS
'return $_[0]->{id}
