[Rails] Re: RAILS not SCALABLE?

I havent had the luxury of having scaling issues myself yet, but I if an application has trouble handling high volumes of traffic, then the framework is only one of several possible causes for these issues. A more likely cause for the issues are the programmers and not the framework. If you are int

Re: [Rails] RAILS not SCALABLE?

On 21 April 2010 23:59, David Zhu wrote: > But I know there are downsides to Rails too. One of them is > scalability. What on earth does that mean? You don't *know* that a downside of Rails is its scalability if you don't know what scalability means. You may well have *heard* or read it said

[Rails] Re: Calling destroy on a model that has no id column

If you want Rails to support composite primary keys you need to install a gem. Here's the projects github page: http://github.com/drnic/composite_primary_keys On Apr 22, 7:27 am, soldier <8863...@gmail.com> wrote: >      # File rails-2.3.2/activerecord/lib/active_record/base.rb, line 2576 > 2576:

[Rails] Re: ActionController::RoutingError after using scaffold

My guess is that you havent specified what the primary_key of the users table is. Rails expect it do be "id" if you dont specify it. Try adding "set_primary_key(:user_id)" to your user model if you havent already. On Apr 22, 8:38 am, William Lang wrote: > Hey there, > > I'm new to Ruby and was fo

Re: [Rails] RAILS not SCALABLE?

On Wed, Apr 21, 2010 at 3:59 PM, David Zhu wrote: > Heyyy > > First off, I love rails. Even thuogh I'm not as good as some of you > guys here, but hey, I started couple months ago, and I am still on my > way learning more. > > > But I know there are downsides to Rails too. One of them is > sca

<    1   2