To add additional point for -1: Marshal uses a binary format and does not guarantee any compatibility with anything except the ruby on the computer which created it. Marshal uses internal format versioning numbers which do not correspond to ruby versions. This means your database backups are potentially non-portable to other OS/ruby/ computer version. This in itself makes this option a non-starter, imho.
You could add the option, but it should never become a default. And even an option should come with a big warning. izidor On 8.10.2008, at 18:23, Frederick Cheung wrote: > > > On 8 Oct 2008, at 17:07, Stephen Celis wrote: > >> >> Here's a ticket for a simple patch to use Marshal instead of YAML for >> attribute serialization. Marshaling is significantly faster (see in >> link), and fixes some YAML load issues (including an outstanding >> ticket). >> >> http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1191-marshal-serialized-attributes >> > While the option is fair enough, I don't thing all existing apps > wouldn't want this turned on "silently": > - if other people use your database yaml is ok as there are parsers > for it in many languages whereas Marshal would be a PITA > - if your existing column is not a blob column (which it wouldn't have > to be previously since yaml generates plain text), the database will > throw a hissy fit (or just truncate the data) when you try to insert a > character that is not legal in the charset used. > - should you be calling string_to_binary if the column supports it ? > > Fred >> Simple enough? >> >> Stephen >>> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
