I think they will work as a good enough repro. I'll let you know when we have a fix. Ivan, are you looking into this?
~Jimmy > -----Original Message----- > From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core- > boun...@rubyforge.org] On Behalf Of Sam Clopton > Sent: Tuesday, January 26, 2010 2:18 PM > To: ironruby-core@rubyforge.org > Subject: Re: [Ironruby-core] Updated Rails instructions > > The database has information that is FOUO. Even though to me it seems that > none of the source code has any of that information (why should it), I don't > really want to send any of it other than snippets just to protect myself. I > should be able to put together a different case at home that has the same > problems as mine. > > If the ActiveRecord unit tests noted above by Shri will work, let me know. > > > > Ivan Porto carrero wrote: > > I'm not seeing that issue atm but I'll work on ironruby-sqlserver > > tonight. > > So if Sam wants to send me a repro I can also look at the cause for his > > problem and hopefully fix it. > > --- > > Met vriendelijke groeten - Best regards - Salutations > > Ivan Porto Carrero > > Blog: http://flanders.co.nz > > Twitter: http://twitter.com/casualjim > > Author of IronRuby in Action (http://manning.com/carrero) > > > > > > > > On Tue, Jan 26, 2010 at 10:06 AM, Jimmy Schementi < > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
