Hi Zak, > > > We want the MySQL server to be: > > > - The best and the most used database in the world > > > > It is surely one of the most used databases, and MySQL was evolving into > > a database with more reasonable features with each version, so why do > > you do some kind of "restart" by using SAP DB? > > MySQL is a combination of a management layer and various storage engines. > The management layer provides a uniform interface to the various storage > engines, while the storage engines provide the bulk of the actual > functionality. > > Integration of SAP DB as a storage engine will not have us "restart" - > instead it will be like the integration of InnoDB and BerkeleyDB as storage > engines. These were both cases where we provided our users with additional > functionality that they could easily start using due to the shared parts of > the management layer.
Does this mean there will be only one version of mysql (with many storage engines) and it will use the SQL-Syntax/parser of mysql? That would mean the current sapdb users won't be able to use the new version without a lot of changes in their code. To quote the statement from SAP: "The rebranded version of SAP DB will be part of MySQL AB's product portfolio in addition to its present product offerings. In this way, the large community of MySQL users gets the alternative of an enterprise-ready database product." This sounded to me like there will be one "original mysql" and one "db formerly known as sapdb" which has all the features of the current sapdb. -- Thomas Butter <[EMAIL PROTECTED]> http://thomas.butter.dk/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
