On Nov 12, 11:06 am, Hongli Lai <[EMAIL PROTECTED]> wrote: > I wrote a simple test > program which performs many database insertions, and the version using > prepared statements is only 1% faster than the version without > prepared statements.
this is just about the most wrong test you could have run. the major speed advantage to prepared statements is that they only get planned once. an insert requires essentially no planning, so there's no benefit. try running your test again with a complex select that join 10 tables but returns only a couple of rows and see the advantage. (plus, there's the whole "free protection from SQL injection" angle, but emulated prepared statements in the DB connector do that job just as well.) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
