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 after sending the above I went to Issuezilla to enter a request.
Then changed my mind and decided to suggest such a change via
the mailing list first.
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 supporting this only for the data sources
that can utilize it, adding another item/option overhead I suppose
--- Question - do the different data sources (SDB, MySQL native, etc)
supply code/configuration options to the query component runtime, or is
that (the query component code) singular and within it accounts for the
different data sources?
Currently in Base:
Open any Base file
Create query def in SQL view - SQLDirect True
call DAYOFWEEK( '2009-11-27' )
Returns a single column named @p0
This RFE would allow the following, with escape processing:
call DAYOFWEEK( :Enter-Current-Date )
Prompts user for value of Enter-Current-Date
Returns single column named @p0
Also,
call CUSTOMFUNCTION( p1...pn )
CUSTOMFUNCTION could return a read only result set containing zero or
more rows, the columns named p0 to p(n-1)
Thanks,
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
