Joe, Just to save you finding another tools documentation less then useful. The YAML website will simply explain how YAML can be used as a configuration tool. That site will contain very little help when it comes to your specific problems of implementation.
I would suggest that the wiki, snippets, forums, and other developers blogs would be a better starting point. There is an abundance of information out there... But an individual developer needs to take some responsibility for holes in their own knowledge. Rather than berating the developers who have invested a large amount of time in producing the symfony project and making if freely available, maybe you could read the book and updated documentation online.... then maybe after that you will feel better informed? I only feel the need to comment as I read the developer list so that I can better understand the symfony project as it develops through its release but your constant bickering is driving me and I'm sure a number of other to despair.. This isn't François by the way On 09/04/2008, Joe Kelsey <[EMAIL PROTECTED]> wrote: > > > Thank you for the reference. The lack of indexing and other search > terms is very frustrating. > > I have only received the printed book last week and am going through > it slowly. > > The online documentation is only as good as the indexing can make it. > The lack of an index is very frustrating. I searched for "fixtures" > and "fixtures.yml" and only came across the reference in unit test > chapter. I will now go to the yaml web site and read there. > > I am not intentionally trying to be rude. I simply write facts down. > If you insist on taking offense to the simple presentation of facts, > then you need to adjust your attitude. My personal attitude is that I > am trying to use a reasonable tool that has some small problems that > the developers apparantly cannot see. > > /Joe > > On Apr 9, 9:54 am, "Francois Zaninotto" <[EMAIL PROTECTED] > > project.com> wrote: > > 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 -~----------~----~----~----~------~----~------~--~---
