D
dbeavon
Guest
I wonder why I'm the first to report it? I suppose it is still pretty unusual for LONGCHAR's to be used by normal ABL programmers (as opposed to CHARACTER). AFAIK there is no other way to handle CLOB's coming in and out of the database. Maybe those are still not used very frequently either. What is really odd to me is that the LONGCHAR works fine on one side of the procedure call, but after it comes over to the receiving procedure, the exact same LONGCHAR (supposedly passed by value ???) is totally different. It is particularly scary for database developers to have to second-guess if/when the data they are passing around will disappear on them. Even a ABL STOP condition, along with the death of the client would be preferable to disappearing data. I was thinking it was a new mechanism for parameter passing in ABL: BY value, BY reference, BY disappearing 
Continue reading...
Continue reading...