[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-glpk] Error literal string too long in TABLE statement

From: Marc Goetschalckx
Subject: [Help-glpk] Error literal string too long in TABLE statement
Date: Fri, 17 Feb 2012 15:04:14 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100216 Thunderbird/3.0.2

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]