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
-~----------~----~----~----~------~----~------~--~---
