Return-Path: Delivered-To: apmail-cayenne-user-archive@www.apache.org Received: (qmail 99761 invoked from network); 12 Sep 2008 20:07:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Sep 2008 20:07:34 -0000 Received: (qmail 71353 invoked by uid 500); 12 Sep 2008 20:07:31 -0000 Delivered-To: apmail-cayenne-user-archive@cayenne.apache.org Received: (qmail 71333 invoked by uid 500); 12 Sep 2008 20:07:31 -0000 Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cayenne.apache.org Delivered-To: mailing list user@cayenne.apache.org Received: (qmail 71322 invoked by uid 99); 12 Sep 2008 20:07:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Sep 2008 13:07:31 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [12.6.244.135] (HELO airmail.wirelessworld.airvananet.com) (12.6.244.135) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Sep 2008 20:06:33 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: DbMerger/MySQL compatibility Date: Fri, 12 Sep 2008 16:06:21 -0400 Message-ID: <8F798BFDA851B943B3A1B2510E928785094C6787@airmail> In-Reply-To: <8F798BFDA851B943B3A1B2510E928785094C676C@airmail> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DbMerger/MySQL compatibility Thread-Index: AckJQsSvnbjB8Xc4R3OZ6elYl6b8swLzFwaQAADweUA= References: <8F798BFDA851B943B3A1B2510E928785092C9BA3@airmail> <8F798BFDA851B943B3A1B2510E928785092C9BDF@airmail> <3A24FB7A-0248-47D9-A851-94A1074BE5B2@pvv.ntnu.no> <8F798BFDA851B943B3A1B2510E928785094C676C@airmail> From: "Scott Anderson" To: X-Virus-Checked: Checked by ClamAV on apache.org Disregard the previous email, I spoke too soon. This is looking like a bug in the MySQL/J driver; it's reporting the field as nullable when it isn't. -----Original Message----- From: Scott Anderson [mailto:sanderson@airvana.com]=20 Sent: Friday, September 12, 2008 3:40 PM To: user@cayenne.apache.org Subject: RE: DbMerger/MySQL compatibility In DbLoader.java, circa line 380, there is a reference to the NULLABLE field. In the ResultSet I'm looking at, there's no such field - there is however an IS_NULLABLE field. -----Original Message----- From: Tore Halset [mailto:halset@pvv.ntnu.no]=20 Sent: Thursday, August 28, 2008 3:19 PM To: user@cayenne.apache.org Subject: Re: DbMerger/MySQL compatibility On Aug 28, 2008, at 21:03, Scott Anderson wrote: >> Is it possible to detect this via jdbc? > > A rather long-winded way to detect table type is: > SHOW CREATE TABLE [table name]; > > This will return the full CREATE TABLE instruction required to rebuild > that table. If this is already how you determine what the fields look > like, it should be trivial to add logic to parse the ENGINE parameter. Currently, I use jdbc metadata only. - Tore.