On Sep 8, 3:58 pm, Iñaki Baz Castillo <[email protected]> wrote: > El Miércoles, 9 de Septiembre de 2009, Jeremy Evans escribió: > > > On Sep 8, 2:59 pm, Iñaki Baz Castillo <[email protected]> wrote: > > > 2009/9/8 Jeremy Evans <[email protected]>: > > > > I tried a variant that set that variables and executed the prepared > > > > statement in a single call to _execute, but it failed some of the > > > > integration tests. It looked to be safe for selects, but did not > > > > return the correct values for delete/insert/update. > > > > Could you show me the code you tryed? > > > Unfortunately, I deleted it when it didn't work. It was a fairly > > trivial change, I'm sure you'd be able to recreate it without much > > difficulty. > > That's what I already tryed. However, all the doc I find about MySQL prepared > statements show me that "SET" and "EXECUTE" are two separate queries. I'll > search more.
They are two separate queries, but the native MySQL adapter allows the sending of multiple statements (separated by semicolons) in a single call. Unfortunately, it didn't seem to work in all cases. 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 -~----------~----~----~----~------~----~------~--~---
