Erm, that should've been "+1 for the *former*", not the latter. ;-)
Jay
>
> At this point I'd just like to know the direction of symfony. Is there
> a plan to support multiple ORM's in the future or will we continue
> down divided roads?
>
>
--~--~-~--~~~---~--~-
+1 for the latter, it bothers me that there are two plugins for a lot of
the more popular plugins because someone decided they need to port it to
Doctrine. Talk about violating the DRY principle. ;-)
Hopefully the Symfony core changes to be "ORM agnostic" as you've said,
as it seems to be th
I've since run into further problems and realize after looking into it
further that your solution seems best. Symfony should be ORM agnostic
if it's going to support more than one ORM. Symfony started by
supporting only propel and now plans to completely support doctrine in
1.1. Although in most a
A great deal of problems are due to the location of the propel schema
(and model) files.
I have designed Doctrine from the beginning so that it would be
possible to have both Doctrine and propel (or other ORMs) running.
(This is why everything that is Doctrine related (schema and model
classes) a
Here is my code to allow the propel-build-model task to ignore
doctrine schema files if the --ignore-doctrine arg is given:
It passes args to _propel_convert_yml_schema(false, 'generated-',
$args) and then uses this logic to ignore doctrine schema files:
if(in_array('--ignore-doctrine',$args)
Well this ticket would probably solve the issue with the S3 plugin:
http://trac.symfony-project.com/trac/ticket/1703
And to extend that Idea it'd be nice to have a flag to ignore doctrine
schemas:
http://trac.symfony-project.com/trac/ticket/1785
On May 24, 8:57 am, "Jonathan H. Wage" <[EMAIL PRO
I don't think symfony will be patched with that logic, but those are the
types of issues you will run in to with having both doctrine & propel,
little annoying things.
- Jon
adventex wrote:
> This actually all started yesterday when we chatted about getting your
> S3 plugin to work within an e
This actually all started yesterday when we chatted about getting your
S3 plugin to work within an existing propel based project. Well, I
have your plugin working and I can successfully crud the doctrine
elements in this propel based project. I think as long as the models
don't need to be linked t
One more thought on converting from propel to doctrine. If we instead
converted one model at a time instead of one module at a time we might
avoid the conflict you mentioned earlier. We'll give it a try and let
you know how it goes.
Jon Todd
On May 24, 7:36 am, "Jonathan H. Wage" <[EMAIL PROTECT
I have not tried myself, but that sounds like it would work if you are
only adding new models to the doctrine schema. I have not tried though.
If you give it a try let us know if it works.
- Jon
adventex wrote:
> Quite simply, assuming my schemas for both ORM's were identical, I'd
> like to be
With google's summer of code supporting doctrine and symfony's planned
support for doctrine in 1.1 do you think we'll see more support for
moving code from propel to doctrine?
'symfony doctrine-import' certainly is helpful but it would be nice to
be able to convert crud generated with propel into
Because the Model class names would be the same for Propel and Doctrine, so
the auto loading would attempt to load 2 classes with the same name, but in
2 different files. You'd have to figure out another way to do it. I thought
about moving the models out of the way so they can't be auto loaded, an
12 matches
Mail list logo
