Ariel Constenla-Haile wrote:
Hi *,UPDATE 'your_table' SET 'your_field' = RTRIM('your_field')depending on the back-end, this statement may have any effect at all (or at least not the desired by John); because in some back-ends, where the field size is strictly respected, whenever you insert/update a field of type char, if the string is shorter than the size specified on the table definition, blank spaces are added. Now can't recall what HSQLDB does (though I recall of some property sql.enforce_strict_size - but neither recall if this is accessible to the OOo Base user, or just in the db properties file [it¡s worth a RFE to make all HSQLDB properties accessible to OOo users]). Regards Ariel.
His fields are of type longvarchar, and I know HSQLDB handles regular varchar fields without enforcing strict field length with this command (I've used it on several occasions myself to remove trailing blanks that were interfering with comparisons). So unless longvarchar fields work differently, using this command from Tools > SQL ought to be successful. Isn't the whole point of the varchar (and presumably longvarchar) definition that the field length is allowed to vary based on content?
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
