Hi there,
is anyone already trying to get postgres fixes which don't break support for other DBs?
I'm currently trying to fix every problem step by step but maybe someone has already fixed it? According to sf.net cvs web there are no interesting checkins since 0.1-20051007 at least not regarding postgres.
Who would like to check my diffs (when finished) and commit them?
Marco Wertejuk wrote:
Hi there,
is anyone already trying to get postgres fixes which don't break support for other DBs?
I'm currently trying to fix every problem step by step but maybe someone has already fixed it? According to sf.net cvs web there are no interesting checkins since 0.1-20051007 at least not regarding postgres.
Who would like to check my diffs (when finished) and commit them?
I'm waiting on CVS access, and then I was thinking to work on postgres support.
But please post your patches. I have my own ideas about what to change, but I don't mind looking at other peoples ideas.
John =:->
| But please post your patches. I have my own ideas about what to change, | but I don't mind looking at other peoples ideas.
Have a look at these patches, there are still some of them missing but I'm trying not to modify sourcecode without having a testcase for the according error.
https://berlin.ccc.de/~marco/rcm-patches/
Hi !!
is anyone already trying to get postgres fixes which don't break support for other DBs?
I just submited to cvs more pear/mdb2 integration modifications that should make rc work with postgres. Testing is need, specially with postgres
-
David Saez Padros -
John Arbash Meinel -
Marco Wertejuk