-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
there is now a pull request to add a compiler pass to the doctrine
bridge https://github.com/symfony/symfony/pull/7599 as well as showing
how this would work with the example of the FOSUserBundle
https://github.com/FriendsOfSymfony/FOSUserBundle/issues/1081
feedback welcome. when i have a go that we do it this way, i will
write a cookbook entry for bundles with reusable entities and the
compiler passes for doctrine mongo/couch/phpcr.
cheers,david
Am 20.02.2013 13:53, schrieb David Buchmann:
> hi,
>
> i want to try to revive an old discussion [1] that never came to
> any conclusion: what would be the right folders for doctrine model
> classes?
>
> with phpcr-odm we start to see clashes between mongo-odm and
> phpcr-odm [2].
>
> the thread went into a discussion that having persistence specific
> classes of your model goes against the whole idea of a database
> abstraction layer. i agree with that. unfortunately this was kind
> of a closing word from me:
>
> "i think we should come to an agreement for the short term future
> to avoid the name clashes richard brought up and improve
> understanding. in the long run, it would be great to find out how
> to further reduce persistence layer specific classes, but that
> won't happen overnight. (i am not saying we should not discuss it
> now - the sooner the better - but we still need a short term
> solution)"
>
> so what do we do? we could start putting our models for phpcr-odm
> in PhpcrDocuments or DocumentsPhpcr. that will fix the collisions
> and further clutter the namespaces of a bundle.
>
> or we could put them in Persistence\Phpcr and hope that orm and
> mongo at some point support that concept or even prefer it over the
> Entity / Document folders so bundles can migrate to that thing. at
> least with those folders we would be open for an approach that says
> for example all doctrines support xml/yml mappings of classes in
> Model plus in Persistence\{dbname} for annotations or cases where
> storage tech specific classes really are needed.
>
> feedback and inputs very welcome. please keep in mind that
> whatever the general ideas are, we do need a solution for phpcr-odm
> that can be implemented quick and keeps compatibility with existing
> doctrine orm / mongo versions.
>
> cheers,david
>
>
> [1]
> https://groups.google.com/forum/#!topic/symfony-devs/BAYC8E6TGsk/discussion
>
>
[2]
> https://groups.google.com/forum/?fromgroups=#!topic/symfony-cmf-devs/5gKhe23UHD0
>
>
- --
Liip AG // Agile Web Development // T +41 26 422 25 11
CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRZBkbAAoJED/JtliXIA4sDQ4IAIVXzwt6S53MBhB+hOkChH0/
UMyTUslIE3JCeCN0QVJkDvCFHfV9rDP8GX1nLNxTo4WH/icEQhYTM9rimxffHV37
y8ngzA9Q1NovLYm655R2eHi+WIDolMuSAN+el/fnEJM0SPPgTxxvUt8a7bMBIvh9
CxZx7WGOqFLQkvyNIBj52yXbbMzycebOL2ye3ETG29NsQRZMhHHhhE0Opt6YwgZB
CGuGvTcb6QFtaqYQ/83Fl9gr/P3KilNwpXjx+/O7aK/I0+Fwf4bk9fRERZXddub6
9AnnezC6ESEs3OQG4murobrh5loJO5XZJL0wcgPul227EKRSyOB/jQ2UNuOirGU=
=Nsjt
-----END PGP SIGNATURE-----
--
--
If you want to report a vulnerability issue on Symfony, please read the
procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
---
You received this message because you are subscribed to the Google Groups
"Symfony developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to symfony-devs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
