tag:blogger.com,1999:blog-19626531.post8729935791151030734..comments2023-11-02T08:32:39.646+01:00Comments on Ola Bini: Programming Language Synchronicity: This is what's wrongOla Binihttp://www.blogger.com/profile/15793488672952593953noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-19626531.post-5996255165218507952007-06-11T20:10:00.000+02:002007-06-11T20:10:00.000+02:00column_type_sql points to the same string as nativ...column_type_sql points to the same string as native[:name] (I'm using C lingo here), so column_type_sql << "something" modifies native[:name], and as Ola pointed out, the native data object is something that usually will be generated only once and cached (not created on every method call),<BR/>so its going to return wrong results on later calls.<BR/>I'm a Ruby newbie so please be gentle if this is off the mark :-)sujeethttps://www.blogger.com/profile/03023033018099287162noreply@blogger.comtag:blogger.com,1999:blog-19626531.post-41480673154458912192007-06-11T16:36:00.000+02:002007-06-11T16:36:00.000+02:00column_type_sql is not an argument though, its a l...column_type_sql is not an argument though, its a local variable. Or do you mean its the return argument? I don't see where anything in native_database_types are being changed. I must be missing something...Anonymousnoreply@blogger.com