How hard would it be to make 'execute' safe for public use, or to
rename it so that a new public method 'execute' could be added? From
an end user perspective, I think db.execute('...') is a much more
readable syntax than db << '...'. Readability not only increases
application maintainability, but also facilitates new user adoption,
and the more developers who know Sequel, the better all of us who use
it will be. :)
Shawn
On Aug 7, 5:43 pm, Jeremy Evans <[email protected]> wrote:
> On Aug 7, 3:11 pm, Shawn Van Ittersum <[email protected]> wrote:
>
> > Is there a reason why db.execute is a public method, if it shouldn't
> > be called from outside Sequel? I had thought it was safe to call
> > because it was public.
>
> Historical behavior/backwards compatibility. When I took over
> maintenance, all of Sequel's methods were public, so there wasn't a
> clear boundary between methods that were internal and methods that
> were for public use. Also, from an OO perspective, it should be
> public, as other objects call it. It's just not designed to be used
> by the end user.
>
> 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
-~----------~----~----~----~------~----~------~--~---
