# Model.save not committing to DB with no errors **URL:** \ **Category:** Rails\ **Created:** [November 19, 2008, 3:07am UTC](https://www.ruby-forum.com/t/model-save-not-committing-to-db-with-no-errors/153585 "2008-11-19T03:07:19Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jkahn](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/53a042/32.png) [@jkahn](https://www.ruby-forum.com/u/jkahn)\ **Post date:** [November 19, 2008, 3:07am UTC](https://www.ruby-forum.com/t/model-save-not-committing-to-db-with-no-errors/153585/1 "2008-11-19T03:07:19Z")
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 ---
**Author:** ![jkahn](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/53a042/32.png) [@jkahn](https://www.ruby-forum.com/u/jkahn)\ **Post date:** [November 19, 2008, 4:49am UTC](https://www.ruby-forum.com/t/model-save-not-committing-to-db-with-no-errors/153585/2 "2008-11-19T04:49:09Z")
On Nov 18, 2008, at 6:04 PM, Joshua K. wrote: > in the console I tried: > =\> 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. Any before\_filters in place on this model? What does your development.log say? Do you see the INSERT query? ---
**Author:** ![jkahn](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/53a042/32.png) [@jkahn](https://www.ruby-forum.com/u/jkahn)\ **Post date:** [November 19, 2008, 7:28am UTC](https://www.ruby-forum.com/t/model-save-not-committing-to-db-with-no-errors/153585/3 "2008-11-19T07:28:47Z")
On Nov 18, 7:48 pm, Philip H. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > 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. j ---
**Author:** ![jkahn](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/53a042/32.png) [@jkahn](https://www.ruby-forum.com/u/jkahn)\ **Post date:** [November 19, 2008, 7:46am UTC](https://www.ruby-forum.com/t/model-save-not-committing-to-db-with-no-errors/153585/4 "2008-11-19T07:46:20Z")
On Nov 18, 10:34 pm, Frederick C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > 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 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 ---
**Author:** ![jkahn](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/53a042/32.png) [@jkahn](https://www.ruby-forum.com/u/jkahn)\ **Post date:** [November 19, 2008, 7:35am UTC](https://www.ruby-forum.com/t/model-save-not-committing-to-db-with-no-errors/153585/5 "2008-11-19T07:35:13Z")
On Nov 19, 6:28 am, Joshua K. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > 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 ---
**Author:** ![jkahn](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/53a042/32.png) [@jkahn](https://www.ruby-forum.com/u/jkahn)\ **Post date:** [November 19, 2008, 7:51am UTC](https://www.ruby-forum.com/t/model-save-not-committing-to-db-with-no-errors/153585/6 "2008-11-19T07:51:00Z")
On Nov 18, 10:34 pm, Frederick C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > 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 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