Re: Sequel::Plugins::PreparedStatements

2012-02-20 Thread Peter van Hardenberg
On Sun, Feb 19, 2012 at 7:34 PM, Jeremy Evans jeremyeva...@gmail.com wrote: If you do that before loading your models, all of your models will use prepared statements for insert/update/delete statements, and lookups by primary key.  I use this in all of my apps. why is this not the default if

Re: Sequel::Plugins::PreparedStatements

2012-02-20 Thread Jeremy Evans
On Feb 20, 12:51 am, Peter van Hardenberg p...@pvh.ca wrote: On Sun, Feb 19, 2012 at 7:34 PM, Jeremy Evans jeremyeva...@gmail.com wrote: If you do that before loading your models, all of your models will use prepared statements for insert/update/delete statements, and lookups by primary

Re: Sequel::Plugins::PreparedStatements

2012-02-20 Thread Jeremy Evans
On Feb 19, 7:44 pm, Jason Dixon ja...@dixongroup.net wrote: On Sun, Feb 19, 2012 at 07:34:40PM -0800, Jeremy Evans wrote: On Feb 19, 5:28?pm, Jason Dixon ja...@dixongroup.net wrote: Does anyone have an example of this plugin in action? It's not immediately clear if/how to use the .apply

Re: Sequel::Plugins::PreparedStatements

2012-02-19 Thread Jeremy Evans
On Feb 19, 5:28 pm, Jason Dixon ja...@dixongroup.net wrote: Does anyone have an example of this plugin in action? It's not immediately clear if/how to use the .apply method. Sequel::Model.plugin :prepared_statements If you do that before loading your models, all of your models will use

Re: Sequel::Plugins::PreparedStatements

2012-02-19 Thread Jason Dixon
On Sun, Feb 19, 2012 at 07:34:40PM -0800, Jeremy Evans wrote: On Feb 19, 5:28?pm, Jason Dixon ja...@dixongroup.net wrote: Does anyone have an example of this plugin in action? It's not immediately clear if/how to use the .apply method. Sequel::Model.plugin :prepared_statements If you

Re: Sequel::Plugins

2007-12-02 Thread Sharon Rosner
Plugin loading is now implemented in the trunk. Each plugin is expected to conform to Wayne and Aman's specification, with the addition of an apply method that takes a model class and an options hash. The implementation is here:

Re: Sequel::Plugins

2007-12-02 Thread Aman Gupta
Thanks Sharon. I made this change so that plugins could accept args in addition to opts: --- lib/sequel/model/plugins.rb (revision 568) +++ lib/sequel/model/plugins.rb (working copy) @@ -4,8 +4,8 @@ class Model class self # Loads a plugin for use with the model class - def

Re: Sequel::Plugins

2007-12-02 Thread Wayne E. Seguin
On Dec 2, 2007 1:50 AM, dusty [EMAIL PROTECTED] wrote: I think this is a great idea! I am continually impressed by this project. I do have a request for the plugins. Do you think you could add a few sentences to each README describing what the plugin does? Dusty, Yes, it is planned

Re: Sequel::Plugins

2007-12-02 Thread Wayne E. Seguin
On Dec 2, 2007 12:01 PM, Sharon Rosner [EMAIL PROTECTED] wrote: We have now defined what Sequel plugins will look like, and how they will be distributed and included. Plugins are rubygems, which means that users can simply require sequel-orderable for example and be able to use the

Re: Sequel::Plugins

2007-12-01 Thread dusty
I think this is a great idea! I am continually impressed by this project. I do have a request for the plugins. Do you think you could add a few sentences to each README describing what the plugin does? I am sure that was already on your timeline, but just in case it wasn't, I think that would