similar to: MySQL sometime fail to record timestamps, become NULL.

With a has_one/belongs_to relationship, what''s the best way to guarantee that the belongs_to object gets created and is accessible alongside the has_one object? I *think* the after_create callback is a good choice, but I discovered an oddity while trying it. F''rinstance, if every horse has a carriage: ============ ActiveRecord::Schema.define do create_table(:horses) {|t|

Anyone have an idea on this? Got a weird situation where on a specific model I can not create an instance using params, yet it works fine on other models. The model which does not work is a stock model, there is no logic in it. Ruby 1.8.7/Rails 3.0.5. Does not work: (rdb:1) PaymentTransaction.create(:purchase_id => 3) #<PaymentTransaction id: 2, purchase_id: nil, action: nil, amount: nil,

Hi, I''m having some problem with getting collection_select to return the current value when editing a record. According to everything I''ve seen, there was an issue but it''s been fixed, but I can''t figure out why it isn''t returning the current value as a selected option. I''ve checked the table structures, and both the call_driver.product_line_id

The following short console session illustrates the problem: Loading development environment (Rails 2.3.2) >> topic=BlogTopic.find(4) => #<BlogTopic id: 4, parent: 2, topic: "Topic Four", created_at: "2009-07-13 21:31:22", updated_at: "2009-09-14 00:37:29"> >> topic.inspect => "#<BlogTopic id: 4, parent: 2, topic: \"Topic

I''m doing a request from a Rails app to another Rails app with ActiveResource. When the format on ActiveResource is XML: Content.find(:all)[0,2].map(&:attributes) => [ {"updated_at"=>Mon Apr 27 15:04:32 UTC 2009, "url"=>"www.google.com", "id"=>1, "created_at"=>Mon Apr 27 15:04:32 UTC 2009},

I was reading a book and following the instructions in it. >> class Story < ActiveRecord::Base; end => nil >> story = Story.new => #<Story id: nil, name: nil, url: nil, created_at: nil, updated_at: nil> >> story.class => Story(id: integer, name: string, link: string, created_at: datetime, updated_at: datetime) I do not remember me asking for id, name, link or

Hi, Thanks for a wonderful Getting Started with Rails. I am up to the last section and just added the comments part. So while testing and looking over comments_controller.rb; I see the reference to post_comment_url calll where is this defined. Below is the message I am getting. Thanks ActionController::RoutingError (post_comment_url failed to generate from {:post_id=>#<Post id: 1, name:

First, BRAVO for this wonderful plugin: has_many_polymorphs ! Now my problem: 4 models : Collection, Page, Fragment, Belonging (which is the join table): 1 class Collection < ActiveRecord::Base 2 has_many_polymorphs :elements, 3 :through => :belongings, 4 :from => [:pages, :fragments, :collections], 5 :as => :collector, 6 :parent_order =>

My server is running Rails 2.3.4...am I not doing this correctly or is something borked? >> c=Contact.last => #<Contact id: 24, name: "Larry", email: "larry-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org", phone: 2147483647, account_id: 8, created_at: "2009-11-27 18:16:25", updated_at: "2009-11-27 18:40:08", hide_name: false, hide_phone: false,

I have two objects, QuoteInput and Insured. QuoteInput has one Insured and Insured belongs to QuoteInput. I don''t understand what I''m seeing. I assign an Insured to a QuoteInput. The Insured object has invalid data. I call save! on the quote input. QuoteInput has no validations. I expect two things to happen - 1) an exception should be thrown, indicating that there was a

I have this strange behavior and I don''t undertand why. Here is the thing: I have this record in my payment model: 1.9.3p286 :019 > u.payment.last Payment Load (0.3ms) SELECT "payments".* FROM "payments" WHERE "payments"."user_id" = 10 => [#<Payment id: 37, bank_name: "Mercantil", plan: "Plan Uno", date:

Hi, seem to keep running into a wall here. I can''t find any resources on site navigation that can deal with any model being in the nav, allow nesting, and can dynamically update. So I thought about it for a while, and decided on a MenuItems class, which contained the position of the child in relation to it''s siblings, where the parent and the child were polymorphic. Then a given

I''m running a rails 2.3.5 / ruby 1.8.7 / postgresql 8.4.2 app and have just run into a curious problem. I have several tables that are initialized with data from csv files and I''ve noticed that, when I try to add new data to any of these tables via Table.new I get a PGError on duplicate key. For example: MIGRATION: class CreateNumbers < ActiveRecord::Migration def self.up

Hello All, I am very new to Ruby on Rails and I have a quick question for you all, which is as follows: I have this following line of code in an partial that renders itself on the posts/index view: Created By (User): <%= User.find(:all, :select => ''name'', :conditions => ["id = ?", 1]) %> (I am hard-coding that ''1'' there) Now, when I run

Rails 3.1.3 I have changed a regular scaffold action a bit so that it can save using ajax. All I needed to do was adding ":remote => true" in <div id="script_new"> <%= form_for script, :remote => true do |f| %> <!-- HERE!!! --> <%= f.hidden_field :video_id %> <%= f.text_field :text %> <%= f.submit "save" %>

I have a test/fixtures/users.yml like so: apa: id: 1 username: apa [...] created_at: <%=Time.now.strftime("%Y-%m-%d %H:%M:%S")%> updated_at: <%=Time.now.strftime("%Y-%m-%d %H:%M:%S")%> I don''t like how I''m repeating myself with the strftime bit. Is there some shorter Time method to format time for a (MySQL) datetime field that

So, I wrote some pages which essentially created some articles which are saved to a database, which also include both the "magic" rows ''created_at'' and ''updated_at''. Now, on my development machine I''m running the MySQL-database and everything worked as I wanted it to. On the live server I''ve had to switch to PostgreSQL 8.1 due to

I am running into a problem with two of my tables and the "uninitialized constant" error when using migration. I get the "uninitialized constant Note" when running the following code in my migration file: create_table :notes do |t| t.column :id, :integer t.column :noteshare_id, :integer t.column :title, :string t.column :covered, :string

Hi all ! I''ve written a Character model, each character has many Attributes. My schema.rb looks like this: create_table "characters", :force => true do |t| t.string "first_name" t.string "last_name" t.integer "user_id" t.datetime "created_at" t.datetime "updated_at" end create_table "attributes",

I have a weird problem going on. All of sudden, records for a certain model will not save with #save Please take a look at this: >> p = Payment.new(:payment_reason_id => 1, :payment_method_id => 1, :date => Date.today, :amount => ''5.00'', :payable => Student.find(608)) => #<Payment id: nil, school_id: nil, payment_reason_id: 1, payment_method_id: 1,