I can clarify. The best example for me is sfGuardPlugin. We have to have both the plugin and our personal code's schema in XML (versus YML) in order to establish FKs from our app to sfGuardPlugin.
Another limitation of the YML is there's no support for propel's inheritance... I didn't even no that this existed until I started a project with another symfony developer. Had I known about this, I could have saved myself from making a lot of extra tables. So yeah, let's make the YML schema's as good as the XML ones. -d On 5/10/07, Nicolas Perriault <[EMAIL PROTECTED]> wrote: > > > Matthias Nothhaft a écrit : > > > I'd like to summarize your replies and put them somewhere in the Wiki. > > Thanks in advance for any idea and comment. > > Something that upsets me more and more as I work a lot with plugins is > the propel foreign key limitation when using two or more distinct schema > files, eg. with the sfGuardPlugin and an extended profile table defined > elsewhere. > > A nice improvement should be, as we now work with YAML shema definition > files over XML ones, is to allow a kind of "foreignSchema" attributes or > directive to handle cross schemafiles foreign keys. > > I don't know if I'm clear, but some should get the point ;) > > ++ > > -- > Nicolas Perriault http://www.clever-age.com > Clever Age - conseil en architecture technique > GSM: +33 6 60 92 08 67 Tél: +33 1 53 34 66 10 > > > > -- Dave Dash 612.670.0621 Discover your favorite restaurant: reviewsby.us gtalk: dave.dash --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
