I am targeting a more slim solution though, solving a very specialized problem. As a developer I simply hate needing to change a database table, splitting it up, to make it fit the customers needs. I causes all those SQL statement to be revised.
With the oo2rel mapping layer I have put much thought into the possibility that a project's datastructure actually might need a change when it is live and filled with data. I cannot simply change the structure, recompile my classes and submit them. I somehow need to preserve integrity within the data model as well. I know I cannot come up with a comprehensive tutorial, not even working examples, but this is the background in front of which I need to operate and somehow I feel I am not the only one I am going to keep basic SQL statements, since that's the way developers, not having a degree think in those relational SQL structures as they understand them more easily. Why take something away from them they know. SQL will just be adapted to OO-state in a manner that is readable and understandable at first glance. As I said: not as comprehensive and complete as your project, but I think its targeting a more specific solution, that occurs often enough in everyday life to need support. You didn't discourage me at all, but rather give me an idea, where thing might be going for me in the future. Tnx! I will have a look into MetaL, that's for sure, but I will also continue with the OO2REL project ;-) "Manuel Lemos" <[EMAIL PROTECTED]> schrieb im Newsbeitrag [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > 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 > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
