David Chelimsky wrote:
> On Jul 27, 2010, at 4:10 AM, Bruno Cardoso wrote:
>
>>> have pending migrations, but still have it reset the test database so
>>> it's schema looks like the development database schema?
>>
>> Exactly.
>
> OK. This is not Rails' intent (which is why
> 'db:abort_if_pendi
On Jul 27, 2010, at 4:10 AM, Bruno Cardoso wrote:
> David Chelimsky wrote:
>> On Jul 26, 2010, at 12:36 PM, Bruno Cardoso wrote:
>>
>>> Thanks for the answers.
>>>
>>> What both solutions (from Ashley and David) do is not modify the BD in
>>> anyway, so nothing gets dropped and nothing is creat
David Chelimsky wrote:
> On Jul 26, 2010, at 12:36 PM, Bruno Cardoso wrote:
>
>> Thanks for the answers.
>>
>> What both solutions (from Ashley and David) do is not modify the BD in
>> anyway, so nothing gets dropped and nothing is created. This resolves
>> the problem but what if I want a clea
On Jul 26, 2010, at 12:36 PM, Bruno Cardoso wrote:
> Thanks for the answers.
>
> What both solutions (from Ashley and David) do is not modify the BD in
> anyway, so nothing gets dropped and nothing is created. This resolves
> the problem but what if I want a clean installation in each test run?
On 26 Jul 2010, at 6:36 PM, Bruno Cardoso wrote:
> What both solutions (from Ashley and David) do is not modify the BD in
> anyway, so nothing gets dropped and nothing is created. This resolves
> the problem but what if I want a clean installation in each test run? Is
> there a way to keep my
Bruno Cardoso wrote:
> Thanks for the answers.
>
> What both solutions (from Ashley and David) do is not modify the BD in
> anyway, so nothing gets dropped and nothing is created. This resolves
> the problem but what if I want a clean installation in each test run? Is
> there a way to keep my "
Thanks for the answers.
What both solutions (from Ashley and David) do is not modify the BD in
anyway, so nothing gets dropped and nothing is created. This resolves
the problem but what if I want a clean installation in each test run? Is
there a way to keep my "schema_migrations" table or remov
On Jul 26, 2010, at 11:50 AM, Ashley Moran wrote:
>
> On Jul 26, 2010, at 5:12 pm, Bruno Cardoso wrote:
>
>> Not sure if this is a RSpec problem or Rails but I believe is more a
>> RSpec situation.
>>
>> What happens is that when I run my RSpecs tests all the BD is recreated,
>>
>> ...
>>
>>
On Jul 26, 2010, at 11:12 AM, Bruno Cardoso wrote:
> Hi
>
> Not sure if this is a RSpec problem or Rails but I believe is more a
> RSpec situation.
>
> What happens is that when I run my RSpecs tests all the BD is recreated,
> including the "schema_migration" table, because of this I get a probl
On Jul 26, 2010, at 5:12 pm, Bruno Cardoso wrote:
> Not sure if this is a RSpec problem or Rails but I believe is more a
> RSpec situation.
>
> What happens is that when I run my RSpecs tests all the BD is recreated,
>
> ...
>
> Anyone know how to resolve this?
Hi Bruno
Are you running `rake
Hi
Not sure if this is a RSpec problem or Rails but I believe is more a
RSpec situation.
What happens is that when I run my RSpecs tests all the BD is recreated,
including the "schema_migration" table, because of this I get a problem
saying:
You have 29 pending migrations:
20100628100855 Creat
11 matches
Mail list logo
