Re: OO2relation mapping

Sounds most interesting (and far more ambicious, than what I had in mind). I'll probably do you wrong by not grasping the full extend of the project, but in short, did I get it right: XML2UML2ProgrammingLanguage I know this probably doesn't grasp the whole scope ;-) But it's a VERY interesting project, and I will have a look into it, that's for sure. CU! Dominik "Manuel Lemos" <mlemos@acm.org> schrieb im Newsbeitrag news:3E332D62.8060901@acm.org... > Hello, > > On 01/25/2003 01:40 PM, Dominik Wittenbeck wrote: > > I am currently developing a object to relational mapping layer for PHP. It's > > NOT a simple treat all databases like one kind of layer (although it does > > involve it to preserve extensibility) but an XML based intermediate layer > > that creates both, table structures, following a conventional scheme and PHP > > classes that allow, OO access to these tables. > > I have enclosed the XML file that represents the intermediate layer. Its > > pretty readable even without the XML schema. > > I am currently under development, so don't expect anything useful in less > > than a few weeks > > > > Question: > > Does anyone of you know anyone who has tried something similar, because my > > research on the subject grows thin? Is something like this of public > > interest at all, or would you prefer accessing your datastructure the old > > fashion way? > > You have pretty much describe Metastorage. It is basically a generator > application that lets you model classes of objects that are mapped and > stored in relational database database. > > You just need to to describe your classes also in a XML file with the > class variables, validation rules, relationships between classes and the > types of functions that your application needs to manipulate the classes > objects. > > Metastorage generates all the code for the classes ready to use in your > applications. That includes also a separate class with code to install > the database schema. The resulting classes API is database independent. > This means that you do not need to change your application to use the > same classes with different types databases. Many types of databases are > supported. Still, you do not need to write absolutely any SQL in > anywhere. Metastorage generates adequate code for you where needed. > > I do not mean to discourage from continuing your work, but since there > is a great deal of overlap between Metastorage and what you have in > mind, you are most welcomed at least to eveluate Metastorage if not also > contribute in anyway to its development. > > Metastorage is Open Source and is avaliable here: > > http://www.meta-language.net/news-2002-12-09-metastorage.html > > http://www.meta-language.net/metastorage.html > > > -- > > Regards, > Manuel Lemos >