| metadata vs. business logic [message #76] |
Thu, 15 June 2006 17:27  |
lauxa
Messages: 2
Registered: June 2006
|
Junior Member |
|
|
I am just getting started in php application development and I really like how you have set up your application framework. I especially like that your data array handles one or multiple records and without breaking it into $<field> variables as some reccommend.
I want to use a perl script to generate my table classes from the create sql script. I am considering making my meta-data definitions separate from any business logic and then using multiple inheritence to include them in the $<table> class so that if my table structures change I can regen the meta-data definitions with minimum impact. I just wanted to get your opinion on this and why you did not design it this way. Maybe changing table specifications is an issue that only affects inexperienced programmers like me? Thanks.
|
|
|
|
Radicore Forum
Search
Help
Members
Register
Login
Home
