Oh, how I love the conference season!
After attending the SFI conference in Krakow (which was great, BTW!) I'm ready to go to Prague.I'm going to be at the Euruko 2008 conference. Their program looks really interesting! All things that I like: Ruby, JRuby, testing. Hey, there's even a talk about AOP in Ruby!
I'll be in Prague from Friday afternoon till Sunday evening, and I'm always happy to chat about Rails, TDD, Agile, JRuby.
I'll try to comment about the conference on my Twitter. Peter Cooper is also going to update his twitter. Any other Twitterers in Prague?
See you in Prague!
Thursday, March 27, 2008
Andrzej's Rails tips #9
link_to_remote and GET request
If you're working with link_to_remote and you are surprised with a message like the following:
Only get, put, and delete requests are allowed.
then you just need to know that link_to_remote uses POST request by default. All you need is to do is to add :method => :get to the method call.
Use schema.rb to create a new database
Keep the schema.rb file in your Subversion/Git/Mercurial repository and make sure it's up-to-date. It's very useful when you want to create a database without using migrations. You just call rake db:schema:load.
As the documentation states:
"Note that this schema.rb definition is the authoritative source for your database schema. If you need to create the application database on another system, you should be using db:schema:load, not running all the migrations from scratch. The latter is a flawed and unsustainable approach (the more migrations you'll amass, the slower it'll run and the greater likelihood for issues)."
If you're working with link_to_remote and you are surprised with a message like the following:
Only get, put, and delete requests are allowed.
then you just need to know that link_to_remote uses POST request by default. All you need is to do is to add :method => :get to the method call.
Use schema.rb to create a new database
Keep the schema.rb file in your Subversion/Git/Mercurial repository and make sure it's up-to-date. It's very useful when you want to create a database without using migrations. You just call rake db:schema:load.
As the documentation states:
"Note that this schema.rb definition is the authoritative source for your database schema. If you need to create the application database on another system, you should be using db:schema:load, not running all the migrations from scratch. The latter is a flawed and unsustainable approach (the more migrations you'll amass, the slower it'll run and the greater likelihood for issues)."
Subscribe to:
Posts (Atom)