On Mon, Mar 26, 2012 at 1:31 PM, Richard Shank <[email protected]> wrote:
> I was looking at PHPCR and noticed that we are developing a conflict for > the location of the db specific models. Right now we have CouchDocument for > CouchDB, both Document for both MongoDB and PHPCR, Entity for ORM, Propel > for Propel and typically Model for db agnostic model code, which is often > an abstract class inherited by the db specific model. > > Should we look at creating a best practice naming system? Personally, I > would like to see Model stay in the same capacity, but with the db specific > model, perhaps we should be using CouchDB, ORM, PHPCR, Propel and MongoDB. > In the future, any additional dbs that are supported, like Amazon's > SimpleDB, would go into the directory SimpleDB. > > Any thoughts on this? Funny, I was actually doing some db-agnostic stuff this weekend and wondering some similar things. I agree with how you're suggesting and and would actually prefer to take it a step further and put each of those directories into a Persistence (or whatever) directory so that all DB related code is organized under one directory, instead of spread out into multiple subdirectories in the root bundle directory (I seem to recall Doctrine having issues if Entity was not in the root, but that was a long time ago and I may be completely mistaken). So, instead of: bundledir |__Document |__Entity |__DependencyInjection |__Propel |__etc Do: bundledir |__Persistence | |__CouchDB | |__Entity | |__Propel |__DependencyInjection |__etc --mark -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
