Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7842009
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T16:13:19+00:00 2026-06-02T16:13:19+00:00

I am upgrading from ruby 1.8.7 to ruby 1.9.3. I noticed that there is

  • 0

I am upgrading from ruby 1.8.7 to ruby 1.9.3. I noticed that there is a difference in how YAML serialized fields are being read. Many of my serialized strings are being coerced to integers in the new YAML format. For example:

1.8.7 :010 > "2011_01".to_yaml
 => "--- 2011_01\n" 
1.8.7 :011 > YAML.load("--- 2011_01\n")

1.9.3p125 :001 > YAML.load("--- 2011_01\n")
 => 201101 

What is causing this? Is there a way to either revert to the old behavior in the new ruby, or migrate my fields to the new format?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T16:13:20+00:00Added an answer on June 2, 2026 at 4:13 pm

    Try using syck as the parser:

    ruby-1.9.3-rc1 :001 > YAML::ENGINE.yamler = "syck"
     => "syck" 
    ruby-1.9.3-rc1 :002 > YAML.load("--- 2011_01\n")
     => "2011_01"
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I noticed after upgrading from 4.2 to 4.3.1 that there is no longer a
Given: A rails 2.3.x application currently being upgraded to rails 3. Upgrading ruby from
I am upgrading from the old SecureWebPages that automates the switching between Http and
I'm upgrading from jQuery 1.5.1 -- I've read about the new way to check
I have a hairy set of routes that I'm upgrading from Rails 2 to
After upgrading to Ruby 1.9.3 (from 1.9.2 using system RVM) on Ubuntu 10.04.3, I
I'm upgrading my app from 3.0.9 to 3.2.1 (ruby 1.9.3-p0, rvm, bundler) and one
in upgrading rails app from 2.2.2 to 2.3.9 first error was: D:\web>ruby script/server -trace
I have an existing Rails 2.3.10 app that I'm considering upgrading to Ruby 1.9.2
When upgrading from Ruby 1.8.6 to Ruby Enterprise 1.8.7 p334, the memory size has

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.