Issue 27416 - ParameterNameSubstitution doesn't work for filter
Summary: ParameterNameSubstitution doesn't work for filter
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.1RC
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2004-04-03 19:40 UTC by paisa
Modified: 2017-05-20 10:48 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description paisa 2004-04-03 19:40:12 UTC
ParameterNameSubstitution doesn't handle a parameter name in form control's
"filter" field.  The error message is (from unixODBC 2.2.5 + postgresql 7.3.4),

        [unixODBC] The # of binded parameter < the # of parameter markers;
	Unrecognized key passed to PGAPI_GetInfo.
Comment 1 marc.neumann 2004-04-05 14:26:14 UTC

Say it in other words:

The form property FILTER doesn't handel Parameter, like "FIELD1 = :var1"

Bye Marc
Comment 2 Frank Schönheit 2004-06-22 11:38:50 UTC
->oj: yours
Comment 3 ocke.janssen 2004-08-16 11:06:33 UTC
The statement which is generated when excuting a sub form with a filter is e.g.

SELECT * FROM "public"."subtable" WHERE ( ( "b" = :id2 ) AND ( "id" =
:link_from_id2 ) )

A second parameter is appended which raises the error. The filter condition
should be looked for already defined parameters.
Comment 4 Marcus 2017-05-20 10:48:12 UTC
Reset assigne to the default "".