[erlang-questions] odbc:param_query works in window ?

Ingela Anderton Andin <>
Mon Jan 8 11:07:49 CET 2007


In your particular case it looks like the driver does not support 
parameterized queries, not all drivers do!
However there is still a problem with the released
windows version where all data was "inserted into"/"selected from" the 
database but something broke during the
process of returning the answer to Erlang.  Just before Christmas I 
though I found a pointer error causing this but
on second thought I was mistaken in what was actually  caused the  
problem.  There seems to be a possibility of this
being a windows compiler problem. (We have a pretty old windows 
compiler).  The latest not yet released version of
odbc tries to works around this and seems to works well on windows, but 
I am not totally convinced that the potential compiler problem is the 
real cause. We just added some new test platforms for the odbc 
application and
though it is running well on most platforms there are some of the new 
unixplatforms where there
seems to be a problem.  So  until I can verify what the problem is there 
potential could
still be a nasty pointer error somewhere so the hunt continues...

Ingela - OTP team  

> Message: 2
> Date: Wed, 27 Dec 2006 18:17:19 +0530
> From: "Siddharth Pareek" <>
> Subject: [erlang-questions] odbc:param_query works in window ?
> To: "Erlang" <>
> Message-ID: <00a701c729b5$2bf7fbc0$>
> Content-Type: text/plain; charset="iso-8859-1"
> hi,
>       i was using the parameterzed query in Erlang using the module odbc:param_query. 
> The mesage passed is : odbc:param_query(Ref,"Select count(*) from counter where type=?",[{{sql_varchar,20},["crick"]}]).
>  Below is the error that is generated.
> {error,connection_closed}
> =ERROR REPORT==== 27-Dec-2006::18:15:10 ===
> ** Generic server <0.95.0> terminating
> ** Last message in was {#Port<0.185>,{exit_status,10}}
> ** When Server state == {state,#Port<0.185>,
>                                {<0.35.0>,#Ref<>}
>                                <0.35.0>,
>                                undefined,
>                                on,
>                                true,
>                                true,
>                                on,
>                                connected,
>                                undefined,
>                                0,
>                                [#Port<0.183>,#Port<0.184>
>                                #Port<0.186>,
>                                #Port<0.187>}
> ** Reason for termination ==
> ** {port_exit,does_not_support_param_arrays}
>          Is there any problem in my message passing or I also heard that windows does not support the param_query ....
> Thanks and Regards,
> Siddharth Pareek

More information about the erlang-questions mailing list