isql's form gives wrong output with table has varchar
I'm using IDS 9.30.UC2 and isql 7.31.UC1 running on Redhat 7.1(2.4.18). I discovered that whenever I hv a table which consist of varchar field. E.g. Branch Table branch_code char(3) branch_addr varchar(40,1) It will gave me wrong output in form which generated using isql. I input 1 sample data record in branch table. When run "select * from branch", it produce the result nicely as below : branch_code [BUG] branch_addr [Nightmare with varchar ] BUT when I generated a form by using isql. It gave me the following result :- branch_code [har] branch_addr [ ] Looks like the content of "branch_addr" is being shown in the "branch_code" field. However if I change the field type for branch_addr from varchar() to char() then the output is properly shown in the form. I've another server which has isql 7.30.UC7 and it has no such problem. Is it a known bug for isql 7.31.UC1 ? Is there any patches for this ?
kh teoh wrote: > I'm using IDS 9.30.UC2 and isql 7.31.UC1 running on Redhat > 7.1(2.4.18). > > I discovered that whenever I hv a table which consist of varchar > field. > E.g. > Branch Table > branch_code char(3) > branch_addr varchar(40,1) > > It will gave me wrong output in form which generated using isql. > > I input 1 sample data record in branch table. When run "select * from > branch", it produce the result nicely as below : > branch_code [BUG] > branch_addr [Nightmare with varchar ] > > BUT when I generated a form by using isql. It gave me the following > result :- > branch_code [har] > branch_addr [ ] > > Looks like the content of "branch_addr" is being shown in the > "branch_code" field. > > However if I change the field type for branch_addr from varchar() to > char() then the output is properly shown in the form. > > I've another server which has isql 7.30.UC7 and it has no such > problem. Is it a known bug for isql 7.31.UC1 ? Is there any patches > for this ? I don't know whether it is a known bug, but it sure looks like an actual bug. You should try to upgrade to ISQL 7.32 - and the latest sub-version in there (don't know the number). No guarantee of any sort that your specific problem is fixed there, but there won't be a fix in the 7.31 code line if it is a new bug - it would only be fixed in the 7.32 versions. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/
> I don't know whether it is a known bug, but it sure looks like an > actual bug. You should try to upgrade to ISQL 7.32 - and the latest > sub-version in there (don't know the number). No guarantee of any > sort that your specific problem is fixed there, but there won't be a > fix in the 7.31 code line if it is a new bug - it would only be fixed > in the 7.32 versions. Where can I download isql 7.32 ? IBM site doesn't seems to allow download anymore. I downloaded isql 7.31 from informix site a year ago.