I figured out the issue.
It turns out that the sqlite3-ironruby adapter uses System::Int64 for the
primary key column. This type is not checked for in the quoting logic of
active record so it just serialize it into the yaml representation of the
object.
I'll need to dig into the sqlite source to
I wanted to try out IronRuby running rails.
I was following the
http://ironruby.net/Documentation/Real_Ruby_Applications/Rails tutorial
using the sqlite instructions.
I began writing my tests and found that I was not able to assign a object to
a belongs to relationship and have it persist to the
09 8:16 AM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] IronRuby and ActiveRecord
Those beginning MRI steps on
http://ironruby.net/Documentation/Real_Ruby_Applications/Rails can probably
just be run with IronRuby. Don't bother customizing the gem path either. Step 7
and
yforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Turpin, Jay
Sent: Friday, November 20, 2009 7:02 AM
To: ironruby-core@rubyforge.org
Subject: [Ironruby-core] IronRuby and ActiveRecord
Hi - I've looked around and haven't been able to find a current set of
instr
Hi - I've looked around and haven't been able to find a current set of
instructions. What is the preferred way to setup IronRuby 0.9.2 with MSSQL and
ActiveRecord support? Do I still need to install the MRI, or can IR stand on
its own now?
Thanks
Regards,
Jay Turpin
"I long to accomplish a gre