On 19 May 2010 16:09, Jorge alejandro Mendoza torres
wrote:
> daphonz wrote:
>> Have you tried using:
>>
>> rake db:migrate RAILS_ENV=production
>>
>> -c
>>
>> On May 18, 12:35�pm, Jorge alejandro Mendoza torres
> I already tried the instruction and the migrations were made in the
> production da
daphonz wrote:
> Have you tried using:
>
> rake db:migrate RAILS_ENV=production
>
> -c
>
> On May 18, 12:35�pm, Jorge alejandro Mendoza torres ["id_oficina = ?",
clave[i].to_i])
In my table, all records exist.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because y
Have you tried using:
rake db:migrate RAILS_ENV=production
-c
On May 18, 12:35 pm, Jorge alejandro Mendoza torres wrote:
> When I do a migration, the changes are make in the test database. Does
> anyone know the reason?
>
> In the config/environment.rb file, I have this: ENV['RAILS_ENV'] ||=
>
On May 18, 5:35 pm, Jorge alejandro Mendoza torres wrote:
> When I do a migration, the changes are make in the test database. Does
> anyone know the reason?
>
> In the config/environment.rb file, I have this: ENV['RAILS_ENV'] ||=
> 'production'
>
> And in the db/ folder, it creates a file named
4 matches
Mail list logo