> Ok, let me re-phrase that. Fibers are GREAT. "Just" sounds dismissive. > It's not. What I'm trying to say is that (again, as far as I know) > Neverblock is _not_ an implementation of asynchronous API for > Postgres. So it lets you run multiple connections concurrently. Good. > It still blocks. That thread stalls until the database finishes up > it's query execution. Just not the whole interpreter.
NeverBlock appears to be an implementation of an asynchronous API for Postgres, AFAICT. It uses a single thread + fibers such that the fibers stall until the database finishes up, but not the thread. A question on datamapper's mysql and postgres drivers: I assume they have similar thread friendliness as the 'standard' ruby mysql and postgres drivers, i.e. the postgres driver is ruby thread friendly and the mysql drivers 'stop the world' while waiting for a request to come back? Also another question: what are named parameters you mentioned? Thanks for your help in this. -=R --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
