search for: amillionhitpoints

I have a Rails app that is a directory indexer. It passes the desired directory path in the url. There is a user table, and a permissions table (which contains the volumes each user has permission to see). There is also a volume table, which contains the available volumes, and a path table, which contains the paths to every file available on the machine. [There are other tables, but these

My Rails application requires a very busy worker process running in the background at all times. I am launching this non-interactive process using script/runner. This process is very busy and is communicating with the MySQL server constantly. As I started putting some load on the system to test, I started running into performance issues. I have since discovered that Rails is only using 1

After installing the PessimisticLocking plugin I noticed that ActiveRecord''s count method no longer works (see below). If I remove the plugin it resolves the problem. I need both. Any ideas? I have also read that Pessimistic Locking is now baked into ActiveRecord in Edge Rails. I have tried Rails 1.1.2 and 1.1.4 and that doesn''t seem to be the case. Any idea when

Could somebody point me to some example code? This must be simple, I just can''t find any examples. I need a new view (new.rhtml) to include the creation of a child object. I have a table for servers (Servers) and a table for IP Addresses (Ips). Server has_many :ips Ip belongs_to :server In my new.rhtml I want the IP entered to become a record in the Ips table. The Ips table

I am considering using Ruby to write a service that will run as a back end process and Rails for the web front end / management console. Are there any suggestions or examples of how I might leverage some of the Rails components like ActiveRecord for use by the back end? It would also be nice to program application logic in a way that it could be shared by both the back end Ruby application

I am very new to Rails. After skimming through the documentation over the last several days, I''m struggling with the appropriate use of belongs_to. My main question is whether a model can have several belongs_to declarations. I have not seen any examples online show that usage. If it can, then I would like to know if it''s poor form or what the best practices are around

My application is going to have a work queue of scheduled tasks stored in the DB. This work queue will be shared across multiple Rails app servers. I need a way to ensure that no two servers get the same jobs if multiple servers pop jobs off the top of the queue simultaneously. Is there a fairly simple way to acheive this? Or do I need to come up with some fancy secondary server to dispatch

Shouldn''t update_all be updating lock_version? As you can see from my console session below, it is upating the record (changed running attribute to true and returned 1 to show 1 recored was updated). But it did not increment lock_version. And optimistic locking is working correctly otherwise. As you can see below, lock version = 562 before and after the update_all call but it is