From: M.-A. Lemburg
Date: March 15 1999 7:09pm
Subject: Memory leaks and error in date handling
List-Archive: http://lists.mysql.com/myodbc/31
Message-Id: <36ED5AEC.40C6A345@lemburg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I've just downloaded and installed the latest version of mysql
(mysql-3.22.19b) and myodbc (iodbc-2.50.22a) for Linux.

I'm using mxODBC for Python to talk to MySQL:
	http://starship.skyport.net/~lemburg/mxODBC.html

The memory leaks I found with earlier version of MyODBC are
unfortunately still there... even reconnecting every now
and then doesn't help.

In addition to those leaks, time(stamp) handling
seems to be buggy in case the seconds part includes a fraction,
e.g. 12:34:46.00 will be stored as 00:00:00 and 12:34:45.45
as 34:48:33 (!). Strange enough time handling has worked fine
in previous versions of mysql.

Is there anything I can do to track down the leakage ?

Thanks.
-- 
Marc-Andre Lemburg                               Y2000: 291 days left
---------------------------------------------------------------------
          : Python Pages >>> http://starship.skyport.net/~lemburg/  :
           ---------------------------------------------------------