From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Source code cleanup |
Date: | 2013-01-08 18:25:41 |
Message-ID: | 50EC64A5.10702@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
I'm getting a bunch of compiler warnings when I compile the latest
psqlodbc sources from CVS. I spent some time cleaning those up.
I also got access to a report of a Coverity scan over psqlodbc source
tree. That found a bunch of additional issues, some of which were
genuine (minor) bugs. I'm still in the process of going through the
report, but I fixed some bugs already.
I also wrote a small regression test suite to test with. It only tests a
few of the ODBC functions at the moment, but it's better than nothing,
and it can be easily extended. What do others use for testing psqlodbc?
I pushed the result to a git repository at
git(at)github(dot)com:hlinnaka/psqlodbc.git. It contains the psqlodbc CVS
history, as converted by git cvsimport, and my changes as commits on top
of that. I can also send the changes as patches if that's preferred. Let
me know how to proceed.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Inoue, Hiroshi | 2013-01-10 03:58:30 | Re: Source code cleanup |
Previous Message | Dave Manginelli | 2012-12-11 15:10:26 | Connection dialog behavior of ODBC driver psqlODBC 9.01.0200 vs 8.x on Win XP |