Ramesh: I'm on the fence as to whether or not this feature should be kept and will gladly defer to others, however: I don't think it's particularly confusing (but I come from a VMS background where every file had a version #). I'm not sure how versions play in the microcontainer world, so maybe this would be more trouble for the users than it's worth. I don't understand why the design features, or lack thereof, in "true RDBMS" products must influence our features. In this case, I don't buy it. :-) Cheers, ------- Paul Nittel JBoss Sr. Quality Assurance Engineer Red Hat, Inc. 314-336-2907 (81-62907) Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ ----- Original Message ----- From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; To: teiid-dev(a)lists.jboss.org, teiid-designer-dev(a)lists.jboss.org Sent: Monday, February 8, 2010 10:07:10 AM GMT -06:00 US/Canada Central Subject: [teiid-dev] VDB Versioning Feature In Teiid a VDB is always represented by its name and version. Together they both represented a unique name for VDB. Although a version represents a particular schema version, 1) It is considered as a entirely different schema then that of the original VDB inside the Teiid runtime. 2) Usually version numbers are presented in the repository systems with implicit rollback behavior. Teiid gives no such rollback functionality. 3) Confusion with automatic version upgrade. If a new VDB with same name is deployed, then version on this VDB is upgraded to next numerical number. The user does not even know what that version number is until they use some tool to figure out which version number that VDB is deployed under. This creates confusion. 4) If there are multiple VDB with different version numbers deployed in runtime and client is connecting with no explicit version number, then Teiid connects to "latest" or a VDB at "default" level. This again seems magical than honoring the explicit behavior. 5) Schema version is generally not supported by any RDBMS vendors. 6) In MMx product line this meant to represent the metadata repository version, but Teiid no longer has this concept. 7) It was a way to move production users from one version of the VDB to another with out interruptions. In our opinion, this is more for the development environments than prod. so, we would like to propose to remove this "version" feature from Teiid. If users want they can manage the this through explicit VDB names. Please let us know if you think this feature is worth keeping and why? Thanks Ramesh.. _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev