Well fot tests, you already have this solution:
// lib/test/JobeetTestFunctional.class.php
class JobeetTestFunctional extends sfTestFunctional
{
public function loadData()
{
$loader = new sfPropelData();
$loader->loadData(sfConfig::get('sf_test_dir').'/fixtures');
return $this;
}
}You could do your own "data-load" task for other environments...
++
________________________________
De : Yevgeniy A. Viktorov <[email protected]>
À : [email protected]
Envoyé le : Mardi, 17 Mars 2009, 21h46mn 08s
Objet : Re: Re : [symfony-users] Fixture Files
Hi Loic,
If I am correctly understand, Benjamin wanted to use different
fixtures(files) on per environment basis, but --env=test will only
switch current environment and will use all accessible fixtures anyway.
I think "--dir" option, maybe wrapped into same other task, would be
right solution, see my previous post in this thread, pls.
Thanks.
Loïc Vernet wrote:
> --env=test ?
>
>
> *De :* Benjamin <[email protected]>
> *À :* symfony users <[email protected]>
> *Envoyé le :* Lundi, 16 Mars 2009, 7h23mn 27s
> *Objet :* [symfony-users] Fixture Files
>
>
> How do I specify which fixture files to use on a per environment
> basis? I don't want test data fixtures being added to the production
> database.
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
