Hi Will,

What exception was raised? What is the message from postgres or AR?

Thanks,
Pedro

On Sat, Oct 3, 2009 at 9:10 PM, William Hertling
<[email protected]> wrote:
>
> Hi,
>
> We've been debugging an issue on our production app for the last day,
> and can't figure out what's going wrong.
>
> We have an ActiveRecord model class called Wishitem. On certain
> objects, calling .save fails consistently on heroku. It doesn't fail
> in either sqlite3 or MySQL, so we suspect it must be related to
> Postgres on heroku. (Postgres seems to be my one main issue with
> heroku. We spend more time debugging Postgres oddities than anything
> else.)
>
> Here's the relevant part of the backtrace:
> [GEM_ROOT]/gems/activerecord-2.1.2/lib/active_record/
> connection_adapters/abstract/database_statements.rb:73:in
> `transaction'
> [GEM_ROOT]/gems/activerecord-2.1.2/lib/active_record/transactions.rb:
> 79:in `transaction'
> [GEM_ROOT]/gems/activerecord-2.1.2/lib/active_record/transactions.rb:
> 98:in `transaction'
> [GEM_ROOT]/gems/activerecord-2.1.2/lib/active_record/transactions.rb:
> 106:in `save'
> [GEM_ROOT]/gems/activerecord-2.1.2/lib/active_record/transactions.rb:
> 118:in `rollback_active_record_state!'
> [GEM_ROOT]/gems/activerecord-2.1.2/lib/active_record/transactions.rb:
> 106:in `save'
>
> I'm not even sure what information I would need further to debug this.
> The only difference between this and other objects of the same class
> that consistently succeed is the data in the object, and the same
> object will succeed in sqlite3 and MySQL, but fail in Postgres.
>
> Any hints as to what we should be looking for?
>
> Thanks,
> Will
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to