Dear Joe, Did you read pages 358-361 (Chapter 16) of the symfony book? There is a subsection called 'using linked tables' there, which pretty much explains the way to reference another record in a fixture file.
Now I know what you're going to say: there is no trace of this section in the index, and the book is very badly written, and your bug is still not fixed. Perhaps you're wondering if all the people who send posts to the symfony mailing-list and forum are not fake people, since the framework simply doesn't work at all. There is no way thousands of people could build symfony applications with such a lousy product. I'll tell you what: you are right. There is no such thing as the symfony framework. I write all the posts myself (I have a lot of different identities). I just do that to make fun of people. They look so funny when they start reading the fake book, and realize that this framework stuff is just a con. I know, this is pathetic. When they realize that, people stop trying with symfony and simply switch to Code Ignitor, which is much better. Perhaps you shoud give it a try? Cheers, François 2008/4/9, Joe Kelsey <[EMAIL PROTECTED]>: > > > > > On Apr 5, 12:02 am, Fabien POTENCIER <[EMAIL PROTECTED] > project.com> wrote: > > > The bug IS fixed. > > The bug is NOT fixed. > > > > The fixture file takes class names as main keys, not table names. But > > I'm sure you already know that as it's well described in the symfony > book. > > > There is no documentation on fixtures anywhere in the symfony book > EXCEPT for a small section in the testing chapter which describes > using fixtures.yml to load arbitrary unit-test data. At least, there > is no reference to fixtures.yml in the Index except for the reference > to unit-test data. Specifically, I cannot find any references to > fixtures.yml that specifically describes using names instead of > indexes for key values. > > > > If you think there is still a bug, please open a new ticket, describe > > the problem, attach a patch that fixes the problem with unit tests that > > prove the patch, and prepend the ticket description with [PATCH]. > > > You can demonstrate the bug by simply installing the sfGuardPlugin in > a NEW project, and attempt to build a database and load the fixture. > The load will fail. > > > > The core team read all tickets as they are created. My first reply to > > the ticket was exactly 35 minutes after the ticket creation! And the fix > > was commited less than 24 hours later. > > > I submitted ticket 3291. There is no evidence that anyone else has > ever looked at it. > > > /Joe > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
