Re: [dba-dev] Bug in query

2009-11-28 Thread Drew Jensen
Daniel Käfer wrote: Hello, I use a postgres database and try to make a query with a (PLPG) SQL function in OOo Base. This query needs two parameters: begin_date and end_date. SELECT * FROM f_termine_report( '{1010131}', :begin_date, :end_date ,true, true, true, true) try this With a

Re: [dba-dev] Bug in query

2009-11-28 Thread Drew Jensen
I use a postgres database and try to make a query with a (PLPG) SQL function in OOo Base. This query needs two parameters: begin_date and end_date. SELECT * FROM f_termine_report( '{1010131}', :begin_date, :end_date ,true, true, true, true) try this CALL f_termine_report(

[dba-dev] enhance the Query definition code to recognize CALL (was: Re: [dba-dev] Bug in query)

2009-11-28 Thread Drew Jensen
SELECT * FROM f_termine_report( '{1010131}', :begin_date, :end_date ,true, true, true, true) try this CALL f_termine_report( '{1010131}', :begin_date, :end_date ,true, true, true, true) I don't need to wait for a response I realize that's just a wrong suggestion. Hi, Right

[dba-dev] Re: enhance the Query definition code to recognize CALL

2009-11-28 Thread Drew Jensen
Drew Jensen wrote: The request is to enhance the query parser components to recognize a command such as CALL somefunction( params ) - allowing escape processing for function parameters -- I don't know what the implications are regarding column names -- Also don't know the cost of