Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Improved JDBC driver part 2

From: Radosław Smogura <rsmogura(at)softperience(dot)eu>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Radosław Smogura <mail(at)smogura(dot)eu>, <pgsql-jdbc(at)postgresql(dot)org>, Александър Шопов <lists(at)kambanaria(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Improved JDBC driver part 2
Date: 2010-12-01 13:59:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-jdbc
On Wed, 1 Dec 2010 12:47:13 +0100, Magnus Hagander <magnus(at)hagander(dot)net>
> On Tue, Nov 30, 2010 at 19:49, Radosław Smogura <mail(at)smogura(dot)eu> wrote:
>> Hello,
>> Maybe you are interested about this what I done with JDBC
> <snip>
>> Driver is here
>> is
>> currently JDK 6 compatible (will be not), compressed patch takes about
>> 136kb
>> gziped.
> Is there any particular reason why this work can't be maintained as a
> branch to the main driver? My understanding is your work is based off
> that one? Being able to work like that would make things a lot easier
> to review.
Yes, it's based on this, with CVS subfolders in sources. I don't see any
problems to maintain this as branch. Ah only one need to read something
about CVS & branching.

> That said, such a process would also be a lot easier if the JDBC
> driver wasn't in cvs ;)
Yes, SVN is much more nicer.
> -- 
>  Magnus Hagander
>  Me:
>  Work:

Radosław Smogura

In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2010-12-01 14:00:13
Subject: Re: We really ought to do something about O_DIRECT and data=journalled on ext4
Previous:From: Heikki LinnakangasDate: 2010-12-01 13:53:12
Subject: Re: crash-safe visibility map, take three

pgsql-jdbc by date

Next:From: David FetterDate: 2010-12-01 16:06:58
Subject: Re: [HACKERS] Improved JDBC driver part 2
Previous:From: LewDate: 2010-12-01 12:27:59
Subject: Re: [HACKERS] Improved JDBC driver part 2

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group