I've just added a whole bunch of commits that deprecate various small methods. The major features I plan to deprecate I will be moving into plugins/extensions included with the gem. So in 2.12, if you use the features, you will get deprecation messages. You can then use:
require 'sequel/extension/pagination' or Model.plugin :caching for example, to get the functionality that was deprecated without the deprecation messages. In a future release (after 2.12), the deprecated features will no longer be loaded by default. For the various small methods that were removed, I plan to keep the deprecated.rb files, and just not have them required. That way, you can: require 'sequel' require 'sequel/deprecated' to continue to use the deprecated methods that weren't moved into plugins. I don't guarantee they will all work, though. There was some deprecation where the internals/API of methods were deprecated without the method itself being deprecated. The main example is methods like Dataset#each no longer taking options. When the deprecated methods are removed, there will be no way to get the previous internals/API back. If you have questions or comments about this process, please let me know. Thanks, 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 -~----------~----~----~----~------~----~------~--~---
