0

I was having a OpenStruct value like #<OpenStruct origins=[]>. It was updated to #<OpenStruct table={:origins=>[]}, modifiable=false> automatically. Has anyone else encountered this issues before? Can you please provide a solution.

There is nothing mentioned about this issue in any documentation.

Tom Lord
  • 27,404
  • 4
  • 50
  • 77
Anubhav Goyal
  • 1
  • Can you please provide more context? What is the code that's creating this `OpenStruct`? – Tom Lord Aug 25 '23 at 16:30
  • 3
    Your behavioural change may have been caused by [the separation of positional and keyword arguments in ruby 3.0](https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/). But without context, I cannot say anything for sure. – Tom Lord Aug 25 '23 at 16:32
  • You mean you had this data structure stored somewhere, like marshaled into a DB text field or something? More code needed, voting to close. – smathy Aug 25 '23 at 16:47
  • I have my data stored in sql database there is a table called temp_options each of my options are openstruct so ruby 2.7 and 3.1 giving different results when fetching from them db. As I have shared above. – Anubhav Goyal Aug 26 '23 at 14:08

0 Answers0