It would be very helpful if the core team could define and document
the expected behavior of DatabaseStatements.execute(). The
implementations appear to vary. Most adapters will return some sort of
native result set, SQL Server returns nil and expects a block, DB2 and
Sybase return the affected row count.
So please, will someone in core explain the expected behavior and can
the execute() documentation in the DatabaseStatements module be
updated to reflect the required behavior. Thanks.
My understanding is that the return value of execute is undefined, but
that it shouldn't require a block. The use case is essentially:
"Run this statement, I don't need a return value"
--
Cheers
Koz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" 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/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
