From: Coder <mli...@re...> - 2004-12-10 23:28:25
|
All, I am having trouble understanding how the OI2 architecture models entity relationships in code and susequently referes to the at run time. I have been using Class::DBI for a while now and understand it's mapping quite well - it's pretty straightforward: Each entity/object is represented by a table and that object has relationships (one-to-one, and one-to-many) with other objects. Each object can tell you what it's children are and each child it's parent when queried using the correct method. These are the main functions I am having probelms translating into 'OI2 speak'. Can anyone shed some light? I have looked through the archives, but have to admit am a little more confused. The OI2 Tutorial is good, but uses only a one table, and the Advanced Tutorial does not appear to have been written as yet. I have seen reference to the fact that Class::DBI could be incorporated, but no concrete examples of how. This is the last stumbling block for me before I migrate my apps to OI2, so your assistance is much appreciated. Ticha ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |