model.save not committing to DB with no errors.

rubyonrails-talk
1

I need some help to debug an issue that just came up, and I've never seen before. I have a model, let's call it Allocation, and it has worked in the past (is working now on the live server). It's fairly simple with user_id, size, start (date), expire (date), storage_billing_id, timestamps. I started noticing in my development branch a couple of days ago that it won't save. As I investigate further I see no errors when I attempt to save it just fails and return nil.

in the console I tried:

a = Allocation.new

... # ...assigned all the attributes manually

a.save

=> nil

a.valid?

=> true

a.frozen?

=> false

a.save!

nil

a.errors.full_messages

=>

I've removed some columns and added a column to this model recently, I've tampered with my os x rails installation recently, and I've done a lot of development around this class recently, but which of these issues is most likely the cause I don't know. Any help debugging this would be GREATLY appreciated.

Thanks, j

2

Any before_filters in place on this model? What does your development.log say? Do you see the INSERT query?

3

no before_filters (no filters of any kind). If I follow the development.log while I'm doing an interactive console like above I can see there is no output at all to the log when I do a save. If I immediately try a different model and save it, no problem, and I see some output in the dev log. It is very bazar. I keep thinking I must be using a keyword in the model somewhere, but I can't find any. Maybe I've broken my installation.

j

4

> Any before_filters in place on this model? What does your
> development.log say? Do you see the INSERT query?

no before_filters (no filters of any kind). If I follow the development.log while I'm doing an interactive console like above I can see there is no output at all to the log when I do a save. If I immediately try a different model and save it, no problem, and I see some output in the dev log. It is very bazar. I keep thinking I must be using a keyword in the model somewhere, but I can't find any. Maybe I've broken my installation.

Well if there's something odd with that model you'll have to show it before people can tell you what's wrong. Tip of the day: methods/ associations called transaction are a bad thing.

Fred

5

Haha how did you know? I had just found that out and came back here to post the solution. It turns out I have a model for financial transactions called.... you guessed it 'transaction'. Seemed to be working fine everywhere for a while then I created a polymeric association to the allocation model and I guess this line in the allocation model screwed it up.

class Allocation < ActiveRecord::Base has_one :transaction, :as => :item ...

Thanks, j

6

Haha, how did you know? I just figured it out and was on my way back here to post the solution. I have a model for financial transactions called.... you guess it 'transaction'. It's been working fine for weeks, but I just added a polymorphic association from it to my Allocation model. It appears this was the culprit:

class Allocation < ActiveRecord::Base   has_one :transaction, :as => :item

Thank you very much!!

j