I was also very interested in this. Jimmy, shouldn't plain old ADO support "just work" once this bug is fixed?: ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=4085
<http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=4085>Obviously, plain old ADO will not be the most optimal solution, but I think it may give us something for MSSQL servers right away. Thanks! Best Regards, Kevin Radcliffe On Thu, Apr 22, 2010 at 11:25 PM, Jimmy Schementi < jimmy.scheme...@microsoft.com> wrote: > That's a very good question actually; I know at least one Rails + > DataMapper site that will switch to IronRuby if they can get it working (one > I used to work on), so I'm personally interested in this as well. :) > > Last I checked do_sqlserver wasn't too mature. They don't depend on dbi, so > there will need to be a separate abstraction for ADO and <http://ADO.NET> > ADO.NET. I have more faith in do_sqlite3 working, as there is a .NET API > for sqlite3 (http://sqlite.phxsoftware.com/), and it would be minimal work > to test do_sqlite3 with sqlite-ironruby. > > As far as DataMapper itself, it'd be interesting to run DataMapper with > it's in-memory database to see if IronRuby at-least run it. > > I'll want to look into running datamapper for unit testing sake, but it > would be great if someone signed up to work on the sqlserver and sqlite3 > support. Ryan, you want to head that up, or at least look for a team? > > ~Jimmy > > On Apr 22, 2010, at 9:54 PM, "Ryan Riley" < > <ryan.ri...@panesofglass.org><ryan.ri...@panesofglass.org> > ryan.ri...@panesofglass.org> wrote: > > What's the status of the DataMapper port? I was just trying to use it but > couldn't get the gem installed. I'm interested in helping get this working. > What next steps are needed? > > Thanks, > > Ryan Riley > > Email: <ryan.ri...@panesofglass.org> > <ryan.ri...@panesofglass.org><ryan.ri...@panesofglass.org> > ryan.ri...@panesofglass.org > LinkedIn: > <http://www.linkedin.com/in/ryanriley><http://www.linkedin.com/in/ryanriley><http://www.linkedin.com/in/ryanriley> > http://www.linkedin.com/in/ryanriley > Blog: <http://wizardsofsmart.net/> > <http://wizardsofsmart.net/><http://wizardsofsmart.net/> > http://wizardsofsmart.net/ > Twitter: @panesofglass > Website: <http://panesofglass.org/> > <http://panesofglass.org/><http://panesofglass.org/> > http://panesofglass.org/ > > > On Mon, Oct 26, 2009 at 7:02 AM, Alexander Coles < > <a...@alexbcoles.com><a...@alexbcoles.com><a...@alexbcoles.com> > a...@alexbcoles.com> wrote: > >> Quick +1 to vote this patch up. >> >> I've been working on the JRuby support for the DataMapper ORM and >> DataObjects(.rb) database connectivity layer. These projects rely in >> turn on another project called Extlib, which provides a bunch of >> useful extensions (lazy arrays, thread pools, string extensions) for >> the other two projects. >> >> I pulled down and built the latest IronRuby and running Extlib's >> specs, the lack of Thread#priority appears to be the first blocker in >> our support for IR. >> >> Alex Coles >> >> DataMapper: >> <http://github.com/datamapper/dm-core><http://github.com/datamapper/dm-core><http://github.com/datamapper/dm-core> >> http://github.com/datamapper/dm-core >> DataObjects: >> <http://github.com/datamapper/do><http://github.com/datamapper/do><http://github.com/datamapper/do> >> http://github.com/datamapper/do >> Extlib: >> <http://github.com/datamapper/extlib><http://github.com/datamapper/extlib><http://github.com/datamapper/extlib> >> http://github.com/datamapper/extlib >> >> >> On Mon, Oct 26, 2009 at 6:12 AM, Shay Friedman >> <<shay.fried...@gmail.com><shay.fried...@gmail.com><shay.fried...@gmail.com> >> shay.fried...@gmail.com> wrote: >> > I remembered something like that. Thanks for pointing it out Pascal. >> > Is it going to be incorporated into V1 code? >> > Thanks! >> > Shay. >> > >> > On Mon, Oct 26, 2009 at 1:49 AM, Pascal Normandin >> > < >> > <pascal.norman...@convergentware.com><pascal.norman...@convergentware.com><pascal.norman...@convergentware.com> >> pascal.norman...@convergentware.com> wrote: >> >> >> >> Hello, >> >> >> >> I have done a very basic implementation of a while back but I did not >> >> finish >> >> the modifications to the specs to test this. >> >> >> >> Here are the commits if you want to grab it >> >> >> >> >> >> >> <http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7><http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7><http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7> >> http://github.com/PascalN2/ironruby/commit/3a0373379b79dbe7fff603ad61ab726d7 >> >> de7f305 >> >> >> >> >> <http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b><http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b><http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b> >> http://github.com/PascalN2/ironruby/commit/47f0de87e908981f553732e97f948a33b >> >> 164f202 >> >> >> >> It was decided at some point that there would only be 5 valid values >> >> >> >> -2, -1, 0, 1 and 2 ... mapping to the CLR thread priorities >> >> Lowest, BelowNormal, Normal, AboveNormal and Highest >> >> >> >> If anything lower than -2 is passed in the thread will be assigned >> Lowest >> >> and Highest if above 2. >> >> >> >> Pascal >> >> >> >> -----Original Message----- >> >> From: >> >> <ironruby-core-boun...@rubyforge.org><ironruby-core-boun...@rubyforge.org><ironruby-core-boun...@rubyforge.org> >> ironruby-core-boun...@rubyforge.org >> >> [mailto: >> >> <ironruby-core-boun...@rubyforge.org><ironruby-core-boun...@rubyforge.org><ironruby-core-boun...@rubyforge.org> >> ironruby-core-boun...@rubyforge.org] On Behalf Of Shay Friedman >> >> Sent: October-25-09 3:55 PM >> >> To: <ironruby-core@rubyforge.org> >> >> <ironruby-core@rubyforge.org><ironruby-core@rubyforge.org> >> ironruby-core@rubyforge.org >> >> Subject: Re: [Ironruby-core] Thread Priority >> >> >> >> Is it going to be implemented for V1? >> >> If yes, is it going to work as MRI with numeric values? >> >> >> >> Thanks! >> >> Shay. >> >> >> >> On 10/25/09, Tomas Matousek < >> >> <tomas.matou...@microsoft.com><tomas.matou...@microsoft.com><tomas.matou...@microsoft.com> >> tomas.matou...@microsoft.com> wrote: >> >> > Ruby Thread#priority is not implemented yet. We disabled name >> mangling >> >> > on >> >> > built-ins recently so Thread.Priority property is not callable via >> >> > lower-case name anymore. >> >> > >> >> > Tomas >> >> > >> >> > -----Original Message----- >> >> > From: >> >> > <ironruby-core-boun...@rubyforge.org><ironruby-core-boun...@rubyforge.org><ironruby-core-boun...@rubyforge.org> >> ironruby-core-boun...@rubyforge.org >> >> > [mailto: >> >> > <ironruby-core-boun...@rubyforge.org><ironruby-core-boun...@rubyforge.org><ironruby-core-boun...@rubyforge.org> >> ironruby-core-boun...@rubyforge.org] On Behalf Of Shay Friedman >> >> > Sent: Saturday, October 24, 2009 11:10 PM >> >> > To: ironruby-core >> >> > Subject: [Ironruby-core] Thread Priority >> >> > >> >> > Hi guys, >> >> > >> >> > I've just noticed that something happened to Thread.priority... It >> >> > disappeared. >> >> > I'm talking about Thread's instance attribute - priority. I'm using >> the >> >> > latest code from GitHub. >> >> > >> >> > The only available priority in the Thread instance now is a CamelCase >> >> > priority, which is .Net's Priority attribute... >> >> > >> >> > Take a look at the next REPL session: >> >> > => #<Thread:0x000005e aborting> >> >> >>>> t = Thread.new { puts "Start"; sleep(30); puts "end" } >> >> > tart=> >> >> > #<Thread:0x0000060 run> >> >> >>>> t.priority >> >> > :0: undefined method `priority' for #<Thread:0x0000060 sleep> >> >> > (NoMethodError) >> >> > >> >> >>>> t.Priority >> >> > => Normal >> >> > >> >> > I remember the priority attribute was problematic because it didn't >> >> receive >> >> > numeric values like MRI. Maybe this is related to that? >> >> > >> >> > Thanks, >> >> > Shay. >> >> > >> >> > -- >> >> > -------------------------------------------------- >> >> > Shay Friedman >> >> > Author of IronRuby Unleashed >> >> > <http://www.IronShay.com> >> >> > <http://www.IronShay.com><http://www.IronShay.com> >> http://www.IronShay.com >> >> > Follow me: >> >> > <http://twitter.com/ironshay><http://twitter.com/ironshay><http://twitter.com/ironshay> >> http://twitter.com/ironshay >> >> > ________________________________________ >> _______________________________________________ >> Ironruby-core mailing list >> <Ironruby-core@rubyforge.org> >> <Ironruby-core@rubyforge.org><Ironruby-core@rubyforge.org> >> Ironruby-core@rubyforge.org >> >> <http://rubyforge.org/mailman/listinfo/ironruby-core><http://rubyforge.org/mailman/listinfo/ironruby-core><http://rubyforge.org/mailman/listinfo/ironruby-core> >> http://rubyforge.org/mailman/listinfo/ironruby-core >> > > _______________________________________________ > Ironruby-core mailing list > <Ironruby-core@rubyforge.org> <Ironruby-core@rubyforge.org> > Ironruby-core@rubyforge.org > <http://rubyforge.org/mailman/listinfo/ironruby-core><http://rubyforge.org/mailman/listinfo/ironruby-core> > http://rubyforge.org/mailman/listinfo/ironruby-core > > > _______________________________________________ > 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
