ho-dev
[FEATURE] Replace DBManager's EscapeSequences methods
i think the existing insert- and deleteEscapeSequences are error prone.
for example they will deliver wrong results if the original strings contained '#' or '§' characters.
To get rid of escaping, the use of prepared statements should be considered.
Yes, I would agree prepared statements are preferable, safer and clearer. I think it would be a lot of work to convert all SQL statements into prepared statements, though?
@tychobrailleur work is in progress. the crucial thing is how to migrate all the strings in database with escaped characters. Up to now i have no good idea concerning this. i fear this will become a very long running migration.
