From: hal.hildebrand at me.com (Hal Hildebrand) Date: Fri, 11 Jan 2013 08:55:31 -0800 Subject: [Pljava-dev] Compatibility with Java 1.7 and PostgreSQL 9.2? Is this project still alive? In-Reply-To: <50F018B3.8010200@tada.se> References: <20130110232746.105a633d@james.intern> <622891DB-3ED6-4A37-BDD0-169321496E14@me.com> <50EFBDC4.7070309@tada.se> <50EFEBC6.3040803@tada.se> <50F007DD.7090600@2ndQuadrant.com> <50F018B3.8010200@tada.se> Message-ID: Yes, there are some changes that might not be desirable. Always a good idea to read the change log :). As to the issues, my thought was to make this a flag so the USOE could be conditionally thrown, defaulting to thrown. Hadn't worked on the C code yet, bit that was on my plate. In general, I certainly didn't intend for this to replace the current work. I just threw this out because I solved the generic signature issues and have verified that the code works. Glad people found it useful and I look forward to seeing more work on the fork. Sent from my Tricorder On Jan 11, 2013, at 5:50 AM, Thomas Hallgren wrote: > On 2013-01-11 13:38, Craig Ringer wrote: >> On 01/11/2013 06:39 PM, Thomas Hallgren wrote: >>> On 2013-01-11 01:48, Hal Hildebrand wrote: >>>>> I have a git hub fork where I've worked through these Java 1.6 issues. >>>>> >>>>> https://github.com/Hellblazer/pljava >> I'm a bit worried by the changelog on that. The changes to make failures silent, in particular, are not something I am at all comfortable with, especially as they appear to be a workaround for an ORM or other intermediary. If they're going to be there, surely they should be conditional? "notsupportederror={log|throw|ignore}" ? > Looking closer at the changes, I wasn't too thrilled about that part either. Making it conditional seems to be a very good idea. > >> The sources and build look like they would benefit from a clean-up, so that seems like a good idea - but what's this change going to do to Windows build support? > Seems some work remain to the the native parts building. Perhaps we could establish a decent process around this at GitHub? I.e. we use pljava/pjlava as the base where we enter issues and submit pull-requests? I'm not at all against adding collaborators to the actual project either if that would speed up reviews and acceptance of contributions. Anyone who wants to help, please raise a hand. > > Regards, > Thomas Hallgren > > _______________________________________________ > Pljava-dev mailing list > Pljava-dev at pgfoundry.org > http://lists.pgfoundry.org/mailman/listinfo/pljava-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: