russm wrote: > this is just about the most wrong test you could have run. > the major
Good to know that I was wrong, but the thing is there's practically no documentation on how a "good" prepared statement is supposed to look like. > 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. So are there any good benchmark suites out there? I can come up with an insanely complex SQL query if I take the time, but it'll be totally disconnected with real-world SQL usage. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
