can't use literal values in filters

[gregoryb]

Hi,
When I try using a filter such as:
[user] in ('joe', 'jane')
I get the following error:
UDA-SQL-0477 A literal value is not supported by the database. This operation requires local processing of the data.
I can trick it into working with something like this:
[user] in (lower('joe'), lower('jane'))
But it's cumbersome, and prevents me from using automatic filters.

Obviously, I don't want to use local processing for this. What could be causing this error?
Why won't cognos allow me to use literal values?

[blom0344]

A post-aggregate filter enforces Cognos to first aggregate the data and filter the resultset locally. A pre-aggregate filter should add the filter to the where clause of the query.  The first setting uses local processing, the second should be database only.  How did you set the filter?


And what database are you using?

[gregoryb]

Hi blom, thanks for your reply.

In the filter properties, it says
Application: Before Auto Aggregation
So it's a pre-aggregate filter?
The database I'm using is Postgres. I know that postgres can certainly handle literal values. So why am I getting this error?

[blom0344]

I'm not sure, I would suspect the connectivity to the database. Do you have the opportunity to use other middleware like:


http://www.postgresql.org/about/news/1153/

[gregoryb]

I installed the PGNP OLEDB like you suggested. How do I use it with my cognos framework manager, though? As far as I can tell, it can only use DSNs that have been defined through the "ODBC Data Source Administrator". And I don't see a way to link the pgnp oledb into the odbc data source.

[gregoryb]

any ideas anyone....? :-\

[aydakut]

Did you find the solution somehow?