Re: [JDBC] Couple of patches for jdbc driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I guess my question is, when I submitted the patches after 7.1.2 was released, I was hoping they would be in the next release, 7.1.3 Is there a way for my patches to make it into the next release, which I assume is 7.2? Or, is the current source-tree geared for 7.2 all-along? On 21-Aug-2001 Tom Lane wrote: Ned Wolpert [EMAIL PROTECTED] writes: (You patched this about two months ago.) Specifically, the 1.11 version of jdbc2/PreparedStatment.java file has the patch, but the 7.1.3 released does not. How do we propragate patches into the main branch for releasing? At this point, we don't; it's quite unlikely that there will be a 7.1.4, considering that we hope to be in 7.2 beta within a month. As far as JDBC goes, lots of people seem to be using CVS snapshots quite happily, so I'm not sure an official back-patch is needed anyway. regards, tom lane Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7grT5iysnOdCML0URAjg3AJ9Zb45j8askvzCw4KeJes4Tx6zDSQCffcE7 HgvGPQt1/OnREkzSfG4AS90= =vUv3 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [JDBC] Couple of patches for jdbc driver
-- Start of PGP signed section. I guess my question is, when I submitted the patches after 7.1.2 was released, I was hoping they would be in the next release, 7.1.3 Is there a way for my patches to make it into the next release, which I assume is 7.2? Or, is the current source-tree geared for 7.2 all-along? Good question. We froze jdbc around February 2001 for 7.1.X. At that time, our main jdbc maintainer wasn't available and we didn't have enough jdbc testers to add stuff during the beta period. This issue came up recently in relation to backpatching a python fix, and the conclusion was that jdbc 7.1.X is a hopeless cause and I tend to agree. I had 6 unapplied jdbc patches at the time we released 7.1. They are all now in CVS. Anyone who reports a jdbc problem is encourage to download the CVS JAR at: http://jdbc.fastcrypt.com 7.2 will be different because we now have an active jdbc community of coders and testers. Also, keep in mind most patches aren't backpatched for reliability reasons. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [JDBC] Couple of patches for jdbc driver
I've mentioned it before, but I really think it would nice to decouple the release cycles of the core engine from the interfaces. Make them separate projects. We have sort of done that now by pushing everyone to the CVS version. This makes some sense to me for ODBC and JDBC, which are large and complex enough to deserve the label of separate projects; and moreover they go out of their way to work with multiple server releases. I'm not sure it's appropriate for any of the other interface libraries, though. IIRC, at one time ODBC *was* a separate project, and we decided that that wasn't working too well. Anyone recall the reasons we pulled it into the main CVS tree? Wouldn't do to make the same mistakes twice... regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
