> Afaik we don't use the the asynchronious stuff in Postgres, so we're > not ruby thread friendly. Afaik the standard pg gem also doesn't use > it, so i wonder whether they are ruby thread friendly too. Any > information on that?
The standard pg gem does support the PG async interface. And it implements an async_exec() (or was that exec_async() ?) method which uses the async interface in a Ruby thread friendly way. The standard pg driver is a very good wrapper for the pg client APIs. I am still wondering why DO needs to rewrite every driver from scratch? If they see shortcomings in the current ones, why don't they just contribute their fixes so every one benefits? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
