On Nov 23, 1:53 am, Ciaran Archer <[email protected]> wrote: > It seems the only type that is affected by this is the datetime > column. Does this mean if I leave type conversions off I will need to > manually covert my Java::JavaSql::Timestamp to a string every time I > need to use it?
The types needing conversion are generally date/time/timestamp, decimal/numeric, and blob/clob. Other types are normal Java objects that JRuby converts transparently. You can manually convert the Java::JavaSql::Timestamp objects, or you can just call Java methods on them instead of ruby methods (which will be much faster). > I will try the master branch too at your suggestion. It probably won't make any difference if you are turning type conversion off, but if you leave type conversion on, it should be significantly faster. It is probably possible to make type conversion significantly faster by adding a Java extension to do so (similar to how sequel_pg does type conversion for the postgres adapter in C), but I don't have any experience doing that. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en.
