| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Warren Young | Date: | August 16 2005 6:15pm |
| Subject: | Re: character encoding | ||
| View as plain text | |||
Karima Velasquez wrote:
> character is: \ (backslash).
Of course that will cause problems. This is the escape character in
SQL, used extensively when inserting BLOB data. Again, I believe
MySQL++ would have prevented this problem, because its escape
manipulator would have escaped the backslashes.
If you don't want to use MySQL++, then use mysql_escape_string() (or
mysql_real_escape_string()) in the C API, which MySQL++'s escape
manipulator is based on.
| Thread | ||
|---|---|---|
| • character encoding | Karima Velasquez | 15 Aug |
| • Re: character encoding | Warren Young | 15 Aug |
| • Re: character encoding | Karima Velasquez | 15 Aug |
| • Re: character encoding | Warren Young | 15 Aug |
| • Re: character encoding | Karima Velasquez | 15 Aug |
| • Re: character encoding | Warren Young | 15 Aug |
| • Re: character encoding | Karima Velasquez | 16 Aug |
| • Re: character encoding | Warren Young | 16 Aug |
| • Re: character encoding | Karima Velasquez | 17 Aug |
| • Re: character encoding | Jasper Bryant-Greene | 17 Aug |
