Scott David Daniels schrieb: > Using a relational DBMS is most definitely _not_ premature optimization. > A relational system provides a way to store data so that it is later
I did not mean that using a relational DBMS is premature optimization but not using a ORM because of performance considerations is one . If it turns out that the ORM is a performance problem you can always tune it afterwards. (probably by the DBMS setup, indexes etc.) > structure. The database structures built are as good a DB organization > as code generated by code generation programs: the meaning is obscured, > and the generated (structure / code) is hard to work with. Its just a layer and therefore the endresult is SQL much the same as the one you would hand code. (and you still can use direct SQL if you like with most of them) In any way you have to bridge the logical gap between the relational and the object data model in your programm. So you will end up in building a layer between your persistence code and your problem and domain specific application code, so what you are actually doing is writing an ORM. Not reinventing the wheel every time and using a existing one is IMHO a better approach. -- Mit freundlichen Grüßen, Ing. Gregor Horvath, Industrieberatung & Softwareentwicklung http://www.gregor-horvath.com -- http://mail.python.org/mailman/listinfo/python-list
