A "\n" tokenizer used in a Camel route is not persisted to a MySQL AuditTrail [message #1036688] |
Mon, 08 April 2013 17:35 |
Srinivasan Iyer Messages: 36 Registered: October 2011 |
Member |
|
|
I have defined a Camel route in my Camel Application type where I have a record tokenizer defined with the value tokenizer="\n". However it appears that every whitespace within my record string acts as a separator at runtime rather than the "\n" (EOL) value provided in the route.
Solution: This may be a MySQL behaviour issue. By default the "\n" used for Tokenization (EOL separator) is interpreted literally by MySQL rather than being saved as is in the DB. This may cause the entire Camel route to go haywire. You can fix the problem on your local MySQL instance by adding (or appending) the following property to your my.ini file.
sql-mode="NO_BACKSLASH_ESCAPES"
|
|
|
Powered by
FUDForum. Page generated in 0.03708 seconds