Heikki Linnakangas | 24 Mar 20:37 2014

Handling malloc failure

Hi,

Many of the functions in __handles.c don't handle a NULL result from 
malloc/calloc properly. There are if-checks for it, but then they go 
ahead and reference the NULL pointer anyway. See attached patch.

- Heikki
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Tony Gelsy Sampaio | 19 Mar 16:08 2014
Picon

Mantenha contato comigo através do LinkedIn.

 
 
 
 
 
De Tony Gelsy Sampaio
 
Graduado em Ciência da Computação (UFMT) Especialista em Redes e Computação Distribuída (IFMT)
Cuiabá e Região, Brasil
 
 
 
 
 
 
 

Eu gostaria de adicioná-lo à minha rede profissional no LinkedIn.
-Tony Gelsy

 
 
 
 
 
 
 
Você está recebendo convites de conexão por e-mail. Cancelar inscrição
© 2014, LinkedIn Corporation. 2029 Stierlin Ct. Mountain View, CA 94043, EUA
 
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Daniel Kasak | 12 Mar 07:42 2014
Picon

Teradata and 'SQL_ERROR or SQL_SUCCESS_WITH_INFO but no error reporting API found'

Hi all.

I have to connect to multiple databases via ODBC, so I *assume* I have to use unixODBC ( and not, for example, Teradata's driver manager). The problem is that Teradata's ODBC drivers appear to be pretty bad. If I execute a statement that works, everything is fine. But if I execute something that raises an error, I get:

SQL_ERROR or SQL_SUCCESS_WITH_INFO but no error reporting API found

I've googled for a while and found other people with the same issue, but no solution. What's going on here? Am I correct in assuming that Teradata simply haven't implemented an error reporting API?

Dan
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
ZhengYabin | 1 Mar 02:29 2014
Picon

Issues when cross-compile the freetds using unixODBC

Hi,
        I’m recently using unixODBC and freetds to build a development environment for accessing a remote SQL Server on an arm-linux platform.
Things I’ve already done:
1.build x86 unixODBC with “./configure --prefix=/usr/local/unixODBC-x86”
2. cross-compile build unixODBC with “./configure --prefix=/usr/local/unixODBC-arm --host=arm-linux”

Then I tried to build freetds with unixODBC
3.build x86 freetds with “./configure --prefix=/usr/local/freetds-x86 --with-unixodbc=/usr/local/unixODBC-x86”, the process is good.
4. but when I tried to build arm edition with
“./configure --prefix=/usr/local/freetds-arm --with-unixodbc=/usr/local/unixODBC-arm --host=arm-linux”
it always genarated an error

./configure: line 16574: /usr/local/unixODBC-arm/bin/odbc_config: connot execute binary file
./configure: line 16575: /usr/local/unixODBC-arm/bin/odbc_config: connot execute binary file
configure: error: sql.h not found

It seems the configure script tried to execute the arm-linux edition odbc_config, it will definitely failed.
How to fix the problem to complete the cross-compile build?



发自 Windows 邮件

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Jan Staněk | 18 Feb 10:17 2014
Picon

Manual pages for executables

Hello,
I have created manual pages for undocumented executables iusql (which is
added to isql man page and linked to it), dltest and odbc_config.

As an attachment, I send the man pages plus the patch to isql.1.

Best regards,
Jan

--

-- 
Jan Stanek - Red Hat Associate Developer Engineer - Databases Team
Attachment (dltest.1): application/x-troff-man, 912 bytes
Attachment (iusql.1): application/x-troff-man, 16 bytes
Attachment (odbc_config.1): application/x-troff-man, 2172 bytes
Attachment (unixODBC-isql.1.patch): text/x-patch, 687 bytes
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Anurag Gupta | 7 Jan 10:29 2014
Picon

Request to spin new version of UNIXODBC on PowerPC64 Little Endian system


Hi Nick,

We are in the process of adding support for Little Endian architecture
for IBM Power PC (ppc64le). For this we want to have UNIXODBC package
containing support for this architecture.

In the release tarball and SVN source, I couldn't find ppc64le changes
in any of the autotools file(config.guess, configure, libtool.m4). In 
addition,I found multiple config.guess, configure, libtool.m4 files 
inside the tarball. Since, we are looking at distros to pick up upstream 
release that has ppc64le support, hence requesting you to spin a new 
release w/  ppc64le support.

For this you can use latest libtool and then autoconf your build tree to
create all scripts with ppc64le support. But in this case, since latest
official libtool release doesn't contain changes for ppc64le and
official release is expected in next few months, we have worked with
libtool maintainer to get alpha release that has all the needed bits to
support building on ppc64le. 

Until then, can we request you to spin off a new version of your pkg
using the alpha libtool release (links below) for distros to pick up, or 
if required, I can send patches too

You can pick up the alpha release from either of the below :

ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.gz (1.6MB)
ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.xz (920KB)

Appreciate your quick response.

Thanks!
--

-- 
Regards,
Anurag

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev

Matt Grimm | 4 Nov 22:06 2013
Picon

Bug report and patch for SQLGetConnectAttr.c

Hello,

I found a bug in SQLGetConnectAttr.c that makes it impossible to tell if tracing is disabled. When tracing is explicitly disabled with SQLSetConnectAttr(), SQLGetConnectAttr() still returns SQL_OPT_TRACE_ON.

I've attached a patch to the 2.3.2 release that fixes the issue for me. If the change is acceptable, would you also consider backporting it to 2.3.1?

Thanks,
m.
diff -Naur a/DriverManager/SQLGetConnectAttr.c b/DriverManager/SQLGetConnectAttr.c
--- a/DriverManager/SQLGetConnectAttr.c	2013-04-15 09:41:25.000000000 -0600
+++ b/DriverManager/SQLGetConnectAttr.c	2013-11-04 13:37:31.647027000 -0700
 <at>  <at>  -204,7 +204,7  <at>  <at> 
             }
             else
             {
-                *((SQLINTEGER*)value) = SQL_OPT_TRACE_ON;
+                *((SQLINTEGER*)value) = SQL_OPT_TRACE_OFF;
             }
         }

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Jan Staněk | 22 Oct 13:40 2013
Picon

Manual page for unixODBC

Hello,
I have created manual page describing environmental variables used by
unixODBC - as far as I know, no such page exists.

I was unable to use the ticket system on sourceforge, so I'm sending the
page as an attachment.

Best regards,
Jan
--

-- 
Jan Stanek - Red Hat Associate Developer Engineer - Databases Team
Attachment (unixODBC.7): application/x-troff-man, 1683 bytes
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Nick Gorham | 10 Oct 08:58 2013

Release of 2.3.2

I have taken the pre from the tar and pushed the 2.3.2 release out there 
now.

Onwards :-)

--

-- 
Nick
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev

leluck | 21 Aug 05:06 2013

A memory leak found

Hi:
The memory leak can be met when user configures a wrong path of the driver(or a wrong driver name is passed to "SQLDriverConnect"), in which state UnixODBC calls "iconv_open" and forgets to close it.
It happens in "DriverManager/SQLDriverConnect.c", on line 1213.


_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Andy Lutomirski | 31 Jul 04:05 2013
Picon

do_attr in SQLConnect.c is broken on some myodbc versions (data loss bug)

do_attr in SQLConnect.c does this:

    if ( value_set )
    {
        if (CHECK_SQLSETCONNECTATTR( connection ))
        {
            SQLSETCONNECTATTR(connection,
                        connection -> driver_dbc,
                        attr3,
                        value,
                        sizeof( value ));

That checks for function[61]->func.

My copy of libmyodbc5.so provides SQLSetConnectAttrW and
MySQLSetConnectAttr.  This means that ->funcW and ->funcA get set, but
->func does not (I haven't tried to follow all the machinations
involved in this).

The upshot is that CHECK_SQLSETCONNECTATTR is false.  This causes
SQL_ATTR_AUTOCOMMIT to have no effect if set to false before
SQLDriverConnect gets called.  This is a data loss bug.

--Andy
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev


Gmane