Hi all, when using data type CHAR(n) , values get filled with blanks up to the defined size before storing in the database and before reading, the trailing blanks are stripped off. This behavior is found on most databases and is ok.
When using VARCHAR(n) columns, trailing blanks are stripped off too. This should be avoided or stated clearly in the docs. My feature request is to change this to keep trailing blanks on VARCHARs as on LONG columns. If someone relies on the current handling make it a connection property. Our current problem is storing text fragments for concatenation with blanks on both sides AND being able to search those columns. Sincerely, Dirk Zoettl _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
