From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: /contrib/retep to gborg |
Date: | 2002-10-20 02:17:17 |
Message-ID: | 200210200217.g9K2HHO18719@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I am concerned that removing them may cause instability, particularly in
> > some of the java build scripts. That's why I am suggesting not doing it
> > during beta.
>
> Actually, it looks to me like they belong with the JDBC driver. As long
> as JDBC is in the main distro, I think we should leave contrib/retep
> there too.
Well, the top of the /contrib/retep README has:
Before you ask what retepTools are, they are my personal suite of
utilities. About 90% of them are JDBC related (either they use JDBC, or
I use them in developing the JDBC driver).
It is java, but only tangentially related to the driver. It is very far
from our core functionality and seems better in gborg. Just because it
is java doesn't mean it has to be near jdbc.
> There was some talk of moving JDBC to gborg, but I'm not sure what the
> plan is, if any.
JDBC folks aren't excited about removing from the main cvs until the
vitality of gborg is more proven.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-20 02:30:17 | Re: /contrib/retep to gborg |
Previous Message | Dave Page | 2002-10-19 19:36:35 | Re: /contrib/retep to gborg |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-20 02:30:17 | Re: /contrib/retep to gborg |
Previous Message | Barry Lind | 2002-10-20 00:13:09 | Re: build.xml patch |