The model is writing back solution values through odbc (Windows) when
the error "literal string too long" is generated in parsing the TABLE
statement. Other table statements in the model to read and write work fine.
I have shortened all names as much as possible, but this is a relatively
complex SQL query that cannot be split, i.e. it is for a single SET
operation. Is there a workaround for this error?
How large is the string limit. How can it be increased.
I also suggest that in the next release of GLPK the limit is increase to
a few thousand of characters, say 2500. Current main memory is measured
in the gigabytes, a few k for SQL queries is acceptable.
--
Marc Goetschalckx
Industrial and Systems Engineering
Georgia Institute of Technology, Atlanta, GA, USA
_______________________________________________
Help-glpk mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-glpk
