similar to: Model and Controller relationship

Can someone tell if there is a reason models shouldn''t access the session? Models could easily be made to access the session or some other shared persistant data store such as a file or a table. _This is the problem_, a model needs to know certain information eg. the id of the current user. But the model has no idea about anything outside of its self, because it can''t access

Is it possible to run a Rails application from embedded ruby? I''m thinking of replacing dispaches with a C application which will then call the normal Rails dispaches and so on... Is this do-able? Many thanks, Kris. -- Posted via http://www.ruby-forum.com/.

If I upgrade from my current version 0.14 to the latest version using "gem update rails" do my existing apps need to have the rails structure re-generated to take advantage of changes to rails? If so is there an easy way to do this without loosing my MCV''s? Thanks, Kris.

Hi, I''m trying to figure the most efficient way to model the following. I can think of at least two ways to relate the tables but from a client/server perspective! I''m wondering how to best (and elegantly)relate them from an AR perspective. A project has many people, A person can work on many projects at any time, A project has many roles, A role is performed by a person, A

A couple of questions please: What is the benefit of having more than one Mongrel/Rails instance on the same machine, could one instance not serve as many requests as say three instances? Is Mongrel Cluster a Apache add-in (like mod_*) or a separately running load balancer which runs on a separate port, I could not work it out from the sample Apache config... |# Redirect all non-static

Well, I understand what they do and how, I just don''t get why! It seems to me that any time you would have this relationship between two tables...they should be one table! Agile Rails book gives what seems to me to be a lame example for this. They use the example of an "invoice" and an "order". An invoice belongs to an order and an order has one invoice. Seems

Hello, First of all, I love RoR. I am studying it, and I am finally "getting there". However, I do have a bit of a problem with ActiveRecord''s saving behaviour. Imagine to have Orders (id, name) {has_one:invoice} and Invoices (id, order_id) {belongs_to :order} . If you type: invoice = Invoice.new(...whatever...) an_order.invoice = invoice if invoice fails to save, you

Can I map 2 tables into one class? Is there any pattern, e.g. using ActiveRecord aggregation? Thanks Szczepan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060103/fa2aed7c/attachment.html

Hi ya, I want to add categories to the depot example in the Agile rails book. These are my thoughts: Create a new table called categories with id, title, description, and image fields. Add a new field to the products table called category_id Create a model called Category with "has_many :products" Now I should have a one to many link between the products and categories tables? Now

In my test configuration, I have a Budgetone, an Iaxy and two computers running X-Lite. My server has one X100P in it (no line hooked up yet). Currently, I can call from any phone to any phone except on one, when the caller calls me, I can't hear the caller (using an X-Lite) but the caller can hear me. If I call him, everything works fine. If I pick up another phone while two phones are

Hello People, I have a possibly very lame question. I am fairly new to RoR, and I want to make sure I do it "right". I have a model called Invoice, and one called InvoiceLines. Usual story: the table "invoice" has a 1:n relationship with "invoice_lines", which includes invoice_id. Now... the application will have a "new order" button, which will allow

Hi I''m new to Rails and I''m struggling with a ''has-one'' relationship. I''m trying to save product and image data in seperate tables with one to one relationship. I''m assuming the problem lies in the controller method below but can''t work it out. The models contain the has_one and belongs to statements, and I tried swapping these

Hi, Does anyone knows how to manage transactions in RoR. Thanx

Hi, How do I associate two different tables which have a lookup id (table) as common. I tried the has_many :table2, :through => look_up_table in my table1 model. Any hints? Thanks, Hari -- Posted via http://www.ruby-forum.com/.

Hi, I am doing a project on invoice. For that I have to use a page both for crating new invoices and for updation of existing invoices. The problem is that when an error occures, I can''t maintain the same page for error correction. How can I redirect it from the controller ? Or can I display ruby errors before submit of the page in ruby? Thanks.. Sainaba. -- Posted via

What does everyone on this list think about enhancing scaffolding somehow so that a "has_many" relationship will automatically drop the <select> box into the view to reference the "belongs_to" part of the view? I think scaffolding is great but I am always adding the <select> boxes to reference the parent association. Do you think this would be useful? just a

It occurs to me as a missing feature that there''s no way to indicate a lookup table relationship (as opposed to other sorts of foreign key relationships) in Rails and that the scaffolding generator could recognise this lookup and render a drop-down list automagically for the lookup table. Say you have an Address and a State, and the State is a lookup table. In addresses you have

I realize this is probably a very basic problem but I''m developing my first rails app and running into this problem. I''m trying to write a photoblog application. I have a photo table and an album table. Photo has a to-one relationship to Album. Photo.album_id => Album.id In my view for photo I have a selection list that''s populated with all the available albums.

Hello everyone, First off, I''m trying to generate a discussion here, not provoke an argument or get people upset. Please bear this in mind if/as you read on... To my mind, there''s 3 missing features from scaffolds that would make them a whole lot more useful. These are: - auto-generation of a drop-down list for inputting/updating has_many/belongs_to relationships between

Three tables: users: id clients: id admin_contacts: user_id, client_id class Client has_many :admin_contacts has_many :contacts, :through => :admin_contacts, :foreign_key => :user_id, :class_name => ''User'' end I added the :contacts for ease of use of grabbing the user objects associated with the admin_contact. This all works great, I can grab the Users that