[erlang-questions] ODBC problem if query returns multiple tables
Erlang (INS)
erlang@REDACTED
Wed Mar 14 12:51:22 CET 2007
I have had the same problem sometime ago.
Review the record type in each table; the supported ones by ODBC are (the
listed in the C Erlang port source code):
SQL_CHAR:
SQL_VARCHAR:
SQL_BINARY:
SQL_LONGVARCHAR:
SQL_VARBINARY:
SQL_LONGVARBINARY:
SQL_NUMERIC:
SQL_DECIMAL:
SQL_TINYINT:
SQL_INTEGER:
SQL_SMALLINT:
SQL_REAL:
SQL_FLOAT:
SQL_DOUBLE:
SQL_TYPE_DATE:
SQL_TYPE_TIME:
SQL_TYPE_TIMESTAMP:
SQL_BIGINT:
SQL_BIT:
Hope this helps you.
Regards, Eduardo
_____
De: erlang-questions-bounces@REDACTED
[mailto:erlang-questions-bounces@REDACTED] En nombre de Surindar Sivanesan
Enviado el: Miércoles, 14 de Marzo de 2007 02:45 a.m.
Para: Scott Lystig Fritchie
CC: Erlang
Asunto: Re: [erlang-questions] ODBC problem if query returns multiple tables
Thanks for the reply.
I'm still facing the same problem even though I make the scrollable cursor
option off.
On 3/14/07, Scott Lystig Fritchie <fritchie@REDACTED> wrote:
>>>>> "ss" == Surindar Sivanesan < surindar.shanthi@REDACTED
<mailto:surindar.shanthi@REDACTED> > writes:
ss> I'm having a Store Procedure (SP) which returns 8 tables (MS Sql).
ss> When I use that same SP in odbc:sql_query/2, it returns
ss> {error,"Column type not supported"}.
It has been a while since I've used the Erlang ODBC driver, but I have
a faint memory that the "Column type not supported" can appear because
of attempts to use scrollable cursors. Do you still see the error if
you use this?
{ok, DB} = odbc:connect(DSN_string, [{scrollable_cursors, off}]).
-Scott
_______________________________________________
erlang-questions mailing list
erlang-questions@REDACTED
http://www.erlang.org/mailman/listinfo/erlang-questions
--
with regards,
S.Surindar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20070314/18612aad/attachment.htm>
More information about the erlang-questions
mailing list