Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 57731 invoked from network); 30 Jul 2007 19:17:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jul 2007 19:17:09 -0000 Received: (qmail 40834 invoked by uid 500); 30 Jul 2007 19:17:08 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 40802 invoked by uid 500); 30 Jul 2007 19:17:08 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 40793 invoked by uid 99); 30 Jul 2007 19:17:08 -0000 Received: from Unknown (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2007 12:17:08 -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: domain of rmoazeni@gmail.com designates 66.249.92.173 as permitted sender) Received: from [66.249.92.173] (HELO ug-out-1314.google.com) (66.249.92.173) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2007 19:17:02 +0000 Received: by ug-out-1314.google.com with SMTP id a2so1148ugf for ; Mon, 30 Jul 2007 12:16:41 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=c/ObJcyC/W+XLFZ3kii0lFDEGmSrWWf79Eoj07Pxw78sVL1bwo6QpLooshhqZCig6jP8g70m/9RfU1TyDmYE74EjfmNjRPuzuZc6bPP+SDvf4tK2sEiNLbdENn+UlzXHhNL1UZ/2ojsm+ZEyDXudt/5T74hd45X5z71w0tWSlEk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gcNRO/cryxhfr+BzbMxS/EICBlbzzqfEu7x2n0WWTcwnotECZb6aUaVGLbVGJiyfwn1oG6xGxUdffz8JJH/o3gVSlqWH6B8z4LPceMX4t8N+PmHz/K1aGnWPrjvKAS8+enroU5SAHVW0j94yurkwh1W0Qw9t70GzvqDCEEt1uWM= Received: by 10.78.200.20 with SMTP id x20mr1597596huf.1185823001026; Mon, 30 Jul 2007 12:16:41 -0700 (PDT) Received: by 10.78.159.1 with HTTP; Mon, 30 Jul 2007 12:16:40 -0700 (PDT) Message-ID: <926963240707301216l5b72b5afyed287992f722da52@mail.gmail.com> Date: Mon, 30 Jul 2007 12:16:40 -0700 From: "Ramin Moazeni" To: derby-dev@db.apache.org Subject: Re: JDBC for reading check constraints In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org Hi Dimple I don't think there is a way to retrieve CHECK constraint info. For this, you may have to directly query the Derby system catalogs. You may have to join between constraints catalog with tables catalog and pick out information you need. Ramin On 7/30/07, Dimple Bhatia wrote: > Hi, > I see that Derby has implemented most methods in java.sql.DatabaseMetaData > interface but I did not see any way to retrieve CHECK constraints from the > database in java.sql.DatabaseMetaData. So How does an application retrieve > CHECK constraints from Derby? > > Thanks > Dimple >