Hi Stefan: >Are there any drawbacks for using "upgrade=true" in the connection for any >db-connection of our app? Glad to know you are getting the database version. Isn't it cool? I am not sure regarding the circumstance your application do "upgrade=true". As far as I know, "upgrade=true" is doing a hard copy. Once perform, your database is upgrade to the new version of derby you are running at. I found some document relate to hard upgrade http://docs.sun.com/app/docs/doc/820-2506/gfheb?a=view. Hope this help, Lily
________________________________ From: Stefan Rehlig <[email protected]> To: Derby Discussion <[email protected]> Sent: Monday, September 7, 2009 6:14:28 AM Subject: AW: Database version Ok. I got it. It's one call "values syscs_util.syscs_get_database_property('DataDictionaryVersion');". Thanks for the hint. Are there any drawbacks for using "upgrade=true" in the connection for any db-connection of our app? -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Gesendet: Montag, 7. September 2009 13:28 An: Derby Discussion Betreff: Re: Database version Stefan Rehlig <[email protected]> writes: > Hi, > > how can i get the number of the derby version, that was used to create the > database? Is there any sys procedure available? The query below may help. It tells you the version of the data dictionary, which corresponds to the Derby version that created the database. If you have upgraded the database later (booted the database with a higher version and specified the upgrade=true connection attribute), it will show the version to which it was upgraded, and not the version that created it. ij> values syscs_util.syscs_get_database_property('DataDictionaryVersion'); 1 --------------------------- 10.6 1 row selected -- Knut Anders
