Re: SQL failures, new navigation system and other things

[Max H. <ma...@fl...>]

> > > 	So conclusion: addslasles on strings inserted into DB is
> > > *always* good idea. Problem may occur only if string is addslashed
> > > twice or more times.
> > Yes, exactly. I think the easiest way to handle this is to let the
> > methods in the db backends be the only methods to add slashes. All
> > other methods should not have to care about this.
>
> 	So also icao should be stored as-is without starting addslashes()
> call used? I will be for this. Ugly stripslashes() hack when using icao as
> substitution for human readable station name could be than removed. But
> IMHO this should be done after comming release. It is not majority problem.

I'm not sure what's being suggested here - is the suggestion that
pw_db_mysql:query should perform the escaping? That's silly. addslashes()
should be run at the point that the query SQL is generated...

Yay for a release of 2.0.0 though!

Max