On Mar 18, 2:49 pm, Clive Crous <[email protected]> wrote: > IMO serialization is always something very app centric. If it were me > I'd not even bother with the plugin especially since you said this is > 3.0 so I'm assuming you're not overly concerned with backward > compatibility
There will certainly be some breakage, but I'm trying to keep it compatible as much as possible. I think each method I deprecated falls into one of the following five categories: 1) Is obsolete (e.g. upcase_identifiers, use_parse_tree) 2) Is a bad idea (e.g. Array#to_sql) 3) Is an alias to another method, where I think the other method is a better name (e.g. Dataset#>>, #import, #size, #uniq) 4) Was moved to a plugin/extension (e.g. pagination) 5) Extends the core classes in ways not related to the SQL DSL (e.g. Enumerable#send_each, Range#interval) For the methods where I deprecated just a particular type of use it was usually because it wasn't useful and made the implementation difficult (such as calling Dataset#each with arguments) or it led to confusing behavior (Dataset#[Integer] returning multiple rows). 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 -~----------~----~----~----~------~----~------~--~---
