Thread: Disabling scalar functions in a DSN.
Hi,
I have a few doubts about ODBC scalar function support.
After having installed the driver and created a DSN, is there some flag that can be set to disable support for scalar functions like {fn current_date()}, and in a way that clients can detect by calling SQLGetInfo?
Alternatively, is there a way to configure a DSN so that scalar functions are sent to the database "as themselves", for example {fn current_date()} =====> current_date() ?
Looking in the driver source code, I see a file odbc.sql, that contains Postgres function definitions. What is the purpose of this file? To be able to invoke scalar functions directly without needing the {fn ...} syntax ?
Thanks in advance,
Daniel
I have a few doubts about ODBC scalar function support.
After having installed the driver and created a DSN, is there some flag that can be set to disable support for scalar functions like {fn current_date()}, and in a way that clients can detect by calling SQLGetInfo?
Alternatively, is there a way to configure a DSN so that scalar functions are sent to the database "as themselves", for example {fn current_date()} =====> current_date() ?
Looking in the driver source code, I see a file odbc.sql, that contains Postgres function definitions. What is the purpose of this file? To be able to invoke scalar functions directly without needing the {fn ...} syntax ?
Thanks in advance,
Daniel
(2014/05/21 17:03), Daniel Díaz wrote: > Hi, > > I have a few doubts about ODBC scalar function support. > > After having installed the driver and created a DSN, is there some flag > that can be set to disable support for scalar functions like {fn > current_date()}, and in a way that clients can detect by calling SQLGetInfo? > > Alternatively, is there a way to configure a DSN so that scalar > functions are sent to the database "as themselves", for example {fn > current_date()} =====> current_date() ? > > Looking in the driver source code, I see a file odbc.sql, that contains > Postgres function definitions. What is the purpose of this file? To be > able to invoke scalar functions directly without needing the {fn ...} > syntax ? Currently odbc.sql isn't used. Please look at mapFuncs array in convert.c. For scalar functions not found in the table, {fn xxx(...)} is simply converted to xxx(...). regards, Hiroshi Inoue -- I am using the free version of SPAMfighter. SPAMfighter has removed 10186 of my spam emails to date. Get the free SPAMfighter here: http://www.spamfighter.com/len Do you have a slow PC? Try a Free scan http://www.spamfighter.com/SLOW-PCfighter?cid=sigen