Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E2AB29E9F for ; Thu, 28 Jun 2012 12:59:46 +0000 (UTC) Received: (qmail 27494 invoked by uid 500); 28 Jun 2012 12:59:46 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 27382 invoked by uid 500); 28 Jun 2012 12:59:46 -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 27047 invoked by uid 99); 28 Jun 2012 12:59:45 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jun 2012 12:59:45 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 6C596142840 for ; Thu, 28 Jun 2012 12:59:44 +0000 (UTC) Date: Thu, 28 Jun 2012 12:59:44 +0000 (UTC) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Message-ID: <73629195.66468.1340888384445.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1808792190.15421.1339674942717.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (DERBY-5818) values syscs_util.syscs_get_database_property('DataDictionaryVersion' ) does not return full version information MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403073#comment-13403073 ] Knut Anders Hatlen commented on DERBY-5818: ------------------------------------------- I guess as long as the stored dictionary version in many cases consists of the two most significant digits only, the dictionary_version() function couldn't be relied on to provide the full version number, so it's not that much more useful than reading the property value. I'd be curious to know what the use case is for getting the full version number of the data dictionary. The usefulness of getting the full version number of the product I can understand, but I have a harder time figuring out what an application could use the last two digits in the dictionary version for, as the dictionary format stays the same when only fixpack or point version is changed. > values syscs_util.syscs_get_database_property('DataDictionaryVersion' ) does not return full version information > ---------------------------------------------------------------------------------------------------------------- > > Key: DERBY-5818 > URL: https://issues.apache.org/jira/browse/DERBY-5818 > Project: Derby > Issue Type: Bug > Reporter: Saurabh Kejriwal > Attachments: derby-5818-01-aa-dictionaryVersionFunction.diff > > > Details > ------------ > $ ./sysinfo > ------------------ Java Information ------------------ > Java Version: 1.6.0 > Java Vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre > Java classpath: /scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/lib/derby.jar:/scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/lib/derbynet.jar:/scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/lib/derbytools.jar:/scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/lib/derbyclient.jar > OS name: Linux > OS architecture: i386 > OS version: 2.6.18-164.0.0.0.1.el5xen > Java user name: ansverma > Java user home: /home/ansverma > Java user dir: /scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/bin > java.specification.name: Java Platform API Specification > java.specification.version: 1.6 > java.runtime.version: 1.6.0-b09 > --------- Derby Information -------- > JRE - JDBC: Java SE 6 - JDBC 4.0 > [/scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/lib/derby.jar] 10.8.2.2 - (1181258) > [/scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/lib/derbytools.jar] 10.8.2.2 - (1181258) > [/scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/lib/derbynet.jar] 10.8.2.2 - (1181258) > [/scratch/ansverma/JavaDBnew/db-derby-10.8.2.2-bin/lib/derbyclient.jar] 10.8.2.2 - (1181258) > ------------------------------------------------------ > ----------------- Locale Information ----------------- > Current Locale : [English/United States [en_US]] > Found support for locale: [cs] > version: 10.8.2.2 - (1181258) > Found support for locale: [de_DE] > version: 10.8.2.2 - (1181258) > Found support for locale: [es] > version: 10.8.2.2 - (1181258) > Found support for locale: [fr] > version: 10.8.2.2 - (1181258) > Found support for locale: [hu] > version: 10.8.2.2 - (1181258) > Found support for locale: [it] > version: 10.8.2.2 - (1181258) > Found support for locale: [ja_JP] > version: 10.8.2.2 - (1181258) > Found support for locale: [ko_KR] > version: 10.8.2.2 - (1181258) > Found support for locale: [pl] > version: 10.8.2.2 - (1181258) > Found support for locale: [pt_BR] > version: 10.8.2.2 - (1181258) > Found support for locale: [ru] > version: 10.8.2.2 - (1181258) > Found support for locale: [zh_CN] > version: 10.8.2.2 - (1181258) > Found support for locale: [zh_TW] > version: 10.8.2.2 - (1181258) > ------------------------------------------------------ > Description > ----------------- > I am using Derby 10.8.2.2. I want to get derby version details through SQL. I ran following query to retrieve version information. > $ java -jar /scratch/ansverma/JavaDBnew//db-derby-10.8.2.2-bin/lib/derbyrun.jar ij > ij version 10.8 > ij> CONNECT 'jdbc:derby:test2;user=test2;password=test2'; > ij> values syscs_util.syscs_get_database_property('DataDictionaryVersion'); > 1 > -------------------------------------------------------------------------------------------------------------------------------- > 10.8 > 1 row selected > It did not return full version information (10.8.2.2) for Derby. > Expected result = 10.8.2.2 > Actual result = 10.8 > I want the version details through SQL query. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira