I agree that this could be a stated convention so that future bundles can 
follow it, but how to go about it? A PR to the docs?

I had the same thought: "where will SimpleDB classes go if Document is 
already taken by MongoDB et al?"

On Tuesday, 27 March 2012 07:31:05 UTC+11, Richard Shank 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?
>
> Richard
>
>

-- 
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

Reply via email to