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 PROTECTED]> wrote: > 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 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 together this should work with out a problem. > > > The only issue I run into now is when running 'symfony propel-build- > > model' I get: > > [sfException] > > A schema.yml must only contain 1 database entry. > > > I believe this is caused by the AmazonS3 schema.yml being in a doctrin > > format. Is there a way to gracefully hide that file from the propel- > > build-model pake task? Perhaps patch the pake task to ignore files > > named 'doctrine/*schema.yml', what do you think? > > > If this works then I think it'd be safe to say that propel and > > doctrine can run together in the same project so long as: > > - There are no conflicting class names > > - There is no need to link (foreign key) classes from separate ORM's > > > On May 24, 7:36 am, "Jonathan H. Wage" <[EMAIL PROTECTED]> wrote: > > >> 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 able to use propel for some modules and doctrine for the > >>> newer modules I'm developing. I've been told this is not possible but > >>> I can't see why. Any thoughts? > > >>> We've spent 5 months coding a site using propel and I now see many > >>> areas where doctrine will suit our needs better. It'd be nice to > >>> transition the code over to doctrine module by module so that we can > >>> have a usable site in the meantime. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
