Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id A22366331B8 for ; Wed, 5 May 2010 20:50:07 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 56970-09 for ; Wed, 5 May 2010 23:49:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mail.postgresql.org (Postfix) with ESMTP id 66913632F30 for ; Wed, 5 May 2010 20:50:00 -0300 (ADT) Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3ACCDF4EAD; Wed, 5 May 2010 19:49:55 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 05 May 2010 19:49:55 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=from:to:cc:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=cV9klM9zOW08W4UDNLI79W3BLC0=; b=FlQWxvJwnaa7s/Xq9B/ZOYZw4gnYiUFBw7QTCz7qZ4htGRXPe/WFZObu2Lv7APiYtXkzJCDHD8gMT6RCPZEAdKGOwftnN79fhu8Dc+dUI/Ng5n9oVgS9FuzBmbzJLCH30almeMdapWAbx8jGPMknCa90eHLbSkb50nIxWDhKTqY= X-Sasl-enc: +E+zpquiS5BoQavWNDzQEalESyBuY1n3Qs5boE3ChBGZ 1273103368 Received: from AdamE6400 (DHCP155014.FHCRC.ORG [140.107.155.14]) by mail.messagingengine.com (Postfix) with ESMTPA id 6DDCB1B2A6; Wed, 5 May 2010 19:49:28 -0400 (EDT) From: "Adam Rauch" To: "'Josh Berkus'" Cc: References: <02cb01caebb0$c6b20f50$54162df0$@com> <4BE09FFC.2020600@agliodbs.com> In-Reply-To: <4BE09FFC.2020600@agliodbs.com> Subject: Re: [TEST REPORT] JDBC reports invalid primary key meta data after PK column rename Date: Wed, 5 May 2010 16:49:30 -0700 Message-ID: <03d901caecad$9b3b42d0$d1b1c870$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: Acrr2WbiIPQ/1meyR4+tPaKVrwhYLgA0pciw X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.6 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7 X-Spam-Level: X-Archive-Number: 201005/10 X-Sequence-Number: 93 Just so I'm clear, does this mean that 9.0 provides a way for the JDBC = driver authors to get the correct PK meta data so they can fix this = problem in the 9.0 JDBC driver? If so, it implies that the current and previous JDBC drivers will break = with 9.0, which seems unfortunate... but I suppose it's better than not = being able to work with 9.0 at all. Thanks, Adam -----Original Message----- From: Josh Berkus [mailto:josh@agliodbs.com]=20 Sent: Tuesday, May 04, 2010 3:30 PM To: Adam Rauch Cc: pgsql-testers@postgresql.org Subject: Re: [TESTERS] [TEST REPORT] JDBC reports invalid primary key = meta data after PK column rename Adam, This is an intentional change in behavior. I've contacted the JDBC driver authors about being ready for it in the new release of pgJDBC for 9.0. I'll contact other driver authors as well. --=20 -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com