Author. Re: Integrity constraint and INPUT ARRAY
Posted in 1995
Topics: Stored Procedures & SPL, Connectivity: ESQL/C, 4GL & Embedded SQL
Thanks all who responded me on "Integrity constraint and INPUT ARRAY",
but the problem is not resolved.
Now I can scetch it more clearly. In fact, there are two things:
1. I guess definitions of columns at compiling time is placed into .frm.
I have not found another places where the information can be stored.
When i change table scema and do not recompile a form the problem is active.
And only when I recompile a form while table schema has no no nulls all is ok
2. I can leave empty line of array even when table schema has "no nulls" field
if I do not use in a program the following code
...
DISPLAY record[n] TO screen_record[n].*
...
Any using of screen_record containing no nulls fields in DISPLAY
cause the problem.
Is it a known bug? Is there workaround?
Thanks in advance.
---------------------------------------------------------------
Vadim G. Park | Email: pivot@taxpol.krasnoyarsk.su
Tax Police | Fax : (3912) 27-07-69
Krasnoyarsk, Russia | Voice: (3912) 27-02-83
---------------------------------------------------------------
Below I attached my original text of "Integrity cosntraint and INPUT ARRAY"
>Hi,
>I've got a table with following schema
>
>create table tbl
> ( f1 smallint no null,
> f2 smallint no null,
> f3 smallint no null)>
>The problem is when i modify it with INPUT ARRAY and accidently insert new line
>i can't leave the one, 'cause 4GL says "This field requires an entered value".
>The same occurs when there are no rows retrivied from the table I've done
>nothing and try to exit the INPUT ARRAY. In last case I at least can press
>interrupt key to escape as far as there is nothing to save.
>
>I would not like to change schema because of integrity constraint.
>Is there workaround?