[ http://issues.apache.org/jira/browse/TORQUE-49?page=comments#action_12427622 ] Thomas Fischer commented on TORQUE-49: --------------------------------------
I do not think Torque should be character-set aware on the input side of torque-sql-exec. I'd prefer that even if the xml input is in some specific character set, the output should be in the default platform encoding. If the user wants to change the output encoding of the insert-sql or the input encoding of the torque-sql-exec tasks, he can then set the default output encoding. > Encoding will not be used in insert-sql if it is used in generation task > ------------------------------------------------------------------------ > > Key: TORQUE-49 > URL: http://issues.apache.org/jira/browse/TORQUE-49 > Project: Torque > Issue Type: Bug > Components: Generator > Affects Versions: 3.2 > Reporter: Thoralf Rickert > Priority: Trivial > > My schema.xml is encoded in UTF-8 and torque generates a SQL file in UTF-8. > But when I run "insert-sql" the TorqueSQLExec task decodes the file with the > system encoding because it doesn't know that the SQL file was encoded in > UTF-8. > My current solution is to set the attribute encoding="UTF-8" in the > "torque-sql-exec" task call in my build-torque.xml. > But I think torque should know the encoding of the files that it generates. > It could be set (for example) in the sqldb.map file or by using special > filename extension like .utf8.sql -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
