phpPunk Posted December 21, 2006 Share Posted December 21, 2006 Not looking for a look into OR/M or this or that...what I'm looking for is some unique genuine ideas on how to solve the Single class per physical table problem...For instance, I like to keep each class focused on solely a single table (as much as I can) under some conditions it's merely enough to have dependenant classes return a array of associated ID's which the class can then use...What about when that isn't practical? Or is it?Perhaps denomalizing a schema would make sense...favouring code reuse/readability over finely tuned SQL queries pulling from various tables to return a single resultset...Again, not looking for advice on which OR/M or Data Mapper, etc...to use...i'm looking for input from someone who has personally considered, used, implemented their own DB solutions over the years and what techniques they find work best under given conditions...Cheers :) Quote Link to comment Share on other sites More sharing options...
utexas_pjm Posted December 22, 2006 Share Posted December 22, 2006 [quote] ...favouring code reuse/readability over finely tuned SQL queries pulling from various tables to return a single resultset...[/quote]Perhaps I am not complely understanding your question, what is preventing you from achieving both? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.