4GL compiler crashes on RECORD LIKE definitions when table contains lvarchar types
Posted in 2005
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Data Types & Schema Design
Is this a known issue that i cannot use RECORD LIKE definitions for tables containing lvchar type columns? Informix 4GL version used is 7.32.FC2 on server 9.40.FC3. c4gl crashes with segmentation fault in this case.
If you've defined an array of records then yes it is a known problem with 7.32.FC2
spilker wrote: > Is this a known issue that i cannot use RECORD LIKE definitions for > tables containing lvchar type columns? Informix 4GL version used is > 7.32.FC2 on server 9.40.FC3. c4gl crashes with segmentation fault in > this case. The crash is at best undesirable - but I would not expect I4GL to know how to handle LVARCHAR. I'm not sure how meaningful it is to you, but the rule of thumb is "if it isn't in IDS 7.31, I4GL probably won't support it". (Unless there's a release note that says otherwise, that would mean I4GL will not understand BOOLEAN, INT8, or SERIAL8 as well as LVARCHAR(n).) So, you could report a bug - the compiler should complain that it is an unrecognized type, not core dump. But the most likely fix would be to reject the program without core dumping, rather than to accept it. Agitating for the bigger fix might eventually work, but I wouldn't hold my breath while waiting. (I was briefly thinking that the I4GL code could probably, just about, treat the LVARCHAR as a big CHAR type ... except for the blank padding. If I4GL declared the host variable in the generated ESQL/C as a string type - instead of char type - it would not include trailing blanks.) -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
if I compile with a RECORD LIKE with an lvarchar with 7.32.UC3 I get a c4gl: line 283: 23339: Memory fault No segv , no core dump