On Wed, Dec 3, 2008 at 2:49 PM, James H. <[EMAIL PROTECTED]> wrote: > I was considering using the currently available Ruby-based ODBC API. > Is there a particular reason a C-based API would be required?
Well, one main reason is performance. The DO drivers directly typecast values to the proper Ruby type, so that does not need to happen in Ruby. This is mainly beneficial with large result sets. Other reasons can be that the existing API is not very nice, not actively maintained or hard to map onto the DO interface. All in all the difference in difficulty between writing the C version or a Ruby version based on existing gem would be small, because the DO API is very simple. One other thing to consider too is how hard it is to get the current ODBC adapter up and running, if it would be possible to make that easier, that's another argument for writing our own. Best thing I guess is to just try and see how well it works. That will probably also show whether a C version is warranted or not. -- Regards, Dirkjan Bussink --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
