To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=62664
------- Additional comments from [EMAIL PROTECTED] Mon Aug 21 21:10:03 -0700 2006 ------- jianhuajiao -> fs: >The problem remains: If for a UTF-8 dBase data source, the user enters a >too-long string in the UI, then this string is silently truncated. This is not because of encoding, it caused by the Database schema. When you create a database and using VARCHAR as field's datatype, at the same thime, it will set the max lenght of this field. so it cannot accept data that lenght over the max lenght. confusion: the VARCHAR default value are two: 50 and 254. when you create a new VARCHAR field, the default max lenght is 50. but if you chang the datatype to LONGVARCHAR, and then check back to VARCHAR, the default max lenght is 254. >This should be easy to fix: Instead of silently ignoring the problem in >convertUnicodeStringToLength, throw an error - that's it. convertUnicodeStringToLength solve the exception throwed by convertUnicodeString to get a accepted string. jianhuajiao -> fs, mmeeks 1. using mmeeks's patch and popup an dialog to tell the change to user. 2. throw an error. but the current exception info is error for this problem. it will throw an encoding error infomation. We need to create an new brach to throw the truncated error. or the exception should be throw before convertUnicodeStringToLength or convertUnicodeString is called. I think it should be throw in convertUnicodeString function. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
