From: Rick DeNatale Date: 2011-01-24T21:35:42+09:00 Subject: Re: pg gem 0.10.1 wth Ruby 1.9.2 does not work with method @pg_conn.exec_prepared(stmt_name, paramet On Mon, Jan 24, 2011 at 3:33 AM, Zeno Davatz wrote: > Dear Ben > > We could trace the error down as far as to this file: > > /usr/lib64/ruby/gems/1.9.1/gems/pg-0.10.1/ext/pg.c > > and that files source is C. For a full list of steps, please see: > > http://dev.ywesee.com/wiki.php/Masa/20110124-setup-ramaze#Result > Zeno, Ben asked this: On Mon, Jan 24, 2011 at 2:36 AM, Ben Bleything wrote: > On Sun, Jan 23, 2011 at 11:34 PM, Zeno Davatz wrote: >> the resulting error is: >> >> [snip] > > You don't actually show the exception, only the backtrace. What is the > actual error? Not sure why you broke the threading by the way. You seemed to miss his question, he was asking for the actual exception which was raised, not just the backtrace. From your link this would appear to be: /usr/lib64/ruby/gems/1.9.1/gems/dbd-pg-0.3.9/lib/dbd/pg/statement.rb:71:in `rescue in execute': ERROR: relation "oddb_business_company_name" already exists (DBI::ProgrammingError) This doesn't look like a bug in the pg gem or in Ruby 1.9.2, but with the prepared statement you are executing or the state of the database when you execute it. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Github: http://github.com/rubyredrick Twitter: @RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale