Re: [AppDB] Make screen shots safe from SQL injection

2006-06-27 Thread Tony Lambregts
Chris Morgan wrote: As we've discussed before I'd rather we did a single full pass of manual testing than several full passes. It saves us time in that we don't have to test the same things repeatedly like we would have to do when making changes to things like classes that are used all over the

Re: [AppDB] Make screen shots safe from SQL injection

2006-06-27 Thread Chris Morgan
> > As we've discussed before I'd rather we did a single full pass of manual > > testing than several full passes. It saves us time in that we don't have > > to test the same things repeatedly like we would have to do when making > > changes to things like classes that are used all over the code.

Re: [AppDB] Make screen shots safe from SQL injection

2006-06-27 Thread Tony Lambregts
Chris Morgan wrote: On Monday 26 June 2006 11:38 pm, Tony Lambregts wrote: Chris Morgan wrote: Yes, having quotes around limit values breaks sql queries. I'll incorporate this into the injection change patch. I'm curious as to why the rest of the patch is the same though. It will conflict wh

Re: [AppDB] Make screen shots safe from SQL injection

2006-06-26 Thread Chris Morgan
On Monday 26 June 2006 11:38 pm, Tony Lambregts wrote: > Chris Morgan wrote: > > Yes, having quotes around limit values breaks sql queries. I'll > > incorporate this into the injection change patch. > > > > I'm curious as to why the rest of the patch is the same though. It > > will conflict when

Re: [AppDB] Make screen shots safe from SQL injection

2006-06-26 Thread Tony Lambregts
Chris Morgan wrote: Yes, having quotes around limit values breaks sql queries. I'll incorporate this into the injection change patch. I'm curious as to why the rest of the patch is the same though. It will conflict when the other sql patch is applied. What other sql patch? How will it conflic