Re: [Rails] Gem Rails Version Showing Wrong?

It seems you have installed rails version 2.3, but when you run gem dependency rails, it shows the data for the latest release. Run gem install rails -v 4.2.0 to get the 4.2.0 version Correct me if I am wrong. ᐧ On Sat, Jan 31, 2015 at 11:00 AM, Tiago Rossi wrote: > Hello, and first of all, Im s

[Rails] Gem Rails Version Showing Wrong?

Hello, and first of all, Im starting with ruby and Ive installed into my server, sorry for my newbie question here guys. After install rails when I type *rails -v* it shows *Rails 2.3.18* but after I type g*em dependency rails* it shows Gem rails-4.2.0 and other dependencies. Please, what are th

Re: [Rails] db:migrate error on test after Rails 4.2 update

If I run: bundle exec rake db:drop db:create db:migrate I get error that db:migrate needs to be run with RAILS_ENV=test if I bundle exec rake db:drop db:create db:migrate RAILS_ENV=test I get error regarding duplicate table again If I delete db from postgres management screen then run bundle exec

Re: [Rails] Problem running ruby script with rails42

On 30 January 2015 at 16:43, PandaR1 wrote: > This very simple script was running in 4.1.6 > > require '.\config\config.rb' > require '.\models\transazioni.rb' > > Transazioni.where(isprocessed: 'N').each do |tr| > puts tr.id_transazione + ' ' + tr.transdate.to_s + ' ' + tr.idmaximo.to_s + > ' ' +

[Rails] Re: Problem running ruby script with rails42

P.S. transazioni.rb (model) class Transazioni < ActiveRecord::Base self.table_name = 'TRANSAZIONI_CONTABILI' establish_connection($src_db) end -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and st

[Rails] Problem running ruby script with rails42

This very simple script was running in 4.1.6 require '.\config\config.rb' require '.\models\transazioni.rb' Transazioni.where(isprocessed: 'N').each do |tr| puts tr.id_transazione + ' ' + tr.transdate.to_s + ' ' + tr.idmaximo.to_s + ' ' + tr.codsap end exit database.yml: # DATA SOURCE dataso

[Rails] Re: Update HStore column's values without triggering after_save callbacks

On Friday, January 30, 2015 at 12:54:15 AM UTC+1, JDog wrote: > I'm doing some wonky stuff  and I am at a point where I need to, in an > after_save callback, modify some data and update an hstore column, but not > trigger the save callback again.  > > What methods are available to me? > > How

[Rails] Available for freelance projects

Hi Rails Talk I have some downtime before I start my new job and I'm currently available for remote contracting I am an experienced senior Rails developer (~5 years professional experience) with a particular interest in rapid prototyping, screen scraping, testing, and APIs. If you are looking

Re: [Rails] db:migrate error on test after Rails 4.2 update

On 30 January 2015 at 14:40, Colin Law wrote: > On 30 January 2015 at 14:17, Sean Kelley wrote: >> >> Thanks. Your command line affects development db also which is not ideal. I >> looked up db:test:prepare and it appears to be deprecated in 4.2 >> http://stackoverflow.com/questions/15169894/wh

Re: [Rails] db:migrate error on test after Rails 4.2 update

On 30 January 2015 at 14:17, Sean Kelley wrote: > > Thanks. Your command line affects development db also which is not ideal. I > looked up db:test:prepare and it appears to be deprecated in 4.2 > http://stackoverflow.com/questions/15169894/what-does-rake-dbtestprepare-actually-do > > I decided

Re: [Rails] db:migrate error on test after Rails 4.2 update

Thanks. Your command line affects development db also which is not ideal. I looked up db:test:prepare and it appears to be deprecated in 4.2 http://stackoverflow.com/questions/15169894/what-does-rake-dbtestprepare-actually-do I decided to try it anyway with RAILS_ENV=test but I get same error of

Re: [Rails] db:migrate error on test after Rails 4.2 update

try this: bundle exec rake db:drop db:create db:migrate db:test:prepare Att, [image: --] Antonio Augusto [image: http://]about.me/aaugusto

[Rails] Update HStore column's values without triggering after_save callbacks

I'm doing some wonky stuff and I am at a point where I need to, in an after_save callback, modify some data and update an hstore column, but not trigger the save callback again. What methods are available to me? Thank you! -- You received this message because you are subscribed to the Googl