![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
![]() |
Thu, May 29 2014 6:42 AM | Permanent Link |
Adam Brett Orixa Systems | All my systems are on EDB v2.17.
However when I look at a database in the EDB Manager, under the "Details" section it reads: Catalog Version: 2.05 Is this because I first created the database in EDB 2.05, or what? Is there any need to update the catalog to v 2.17, and if so how do you do it? |
Thu, May 29 2014 7:16 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Adam
>All my systems are on EDB v2.17. > >However when I look at a database in the EDB Manager, under the "Details" section it reads: > >Catalog Version: 2.05 > >Is this because I first created the database in EDB 2.05, or what? > >Is there any need to update the catalog to v 2.17, and if so how do you do it? I don't think you need to worry. I just checked mine and they're all 2.05, even one I created just now to see what happened. Without knowing the internals my guess would be that 2.17 is the engine version and 2.05 the catalog format/layout version. If it make you feel better I have an in-memory database with a catalog version of 0.0 Roy Lambert |
Fri, May 30 2014 8:39 PM | Permanent Link |
Jan Ferguson Data Software Solutions, Inc. ![]() | Adam,
The catalog version will change whenever Tim makes a change in the catalog (meta data). This will never change between builds but can change in a minor or major version update.So the catalog version number and the product version number will usually have different versions, unless Tim has updated the catalog. This was a change Tim made in v2.04. Older versions cannot access any catalog that has been updated using a newer version. Below is part of a post Tim made in 30 Dec 2009 with a subject line of "What is the command to update database metadata on EDB version change?" "As an aside, the next 2.04 release of ElevateDB will have two additional features: 1) The ability to see the version of any given catalog. This is useful for determining if a catalog has been updated yet or not by the current, newer version of ElevateDB. 2) The versioning between table files and the catalog metadata for a table will work on the basis of a matching structure. That is, if you have a catalog file that matches a set of table files currently, and then save it somewhere else (like in a backup), alter the table to add a column, alter the table to drop the same column, and then restore the original catalog file, the table files will still be usuable with the old catalog. Currently, this is not the case, and attempting to do so will result in an error about a version mismatch between the catalog and the table files. " Hope that helps. --------------------- Jan Ferguson [Team Elevate] Adam Brett wrote: > All my systems are on EDB v2.17. > > However when I look at a database in the EDB Manager, under the > "Details" section it reads: > > Catalog Version: 2.05 |
Sat, Jun 21 2014 2:52 PM | Permanent Link |
Michael Riley ZilchWorks | J.B. Ferguson wrote:
> The catalog version will change whenever Tim makes a change in the > catalog (meta data). This will never change between builds but can > change in a minor or major version update.So the catalog version > number and the product version number will usually have different > versions, unless Tim has updated the catalog. This was a change Tim > made in v2.04. +1 -- Michael Riley GySgt USMC (Ret) www.zilchworks.com |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |