From: Aaron H. <aa...@me...> - 2001-10-07 23:23:16
|
From: "Chuck Esterbrook" <Chu...@ya...> > Perhaps they would write: > > "state='%(state)s' and %(field)s=%(value)s and duration>%(duration)s" % > locals() > > Which still isn't so bad. This way works with programmed queries, where the paramters are well know to the developer and the user, but gets ugly when you have optional parameters. I hate the SQL += 'WHERE 1=1 AND' if (DateRange): SQL += ' ( (callDate > %(startDate)s) AND (callDate > %(endDate)s) ) ' if (OneDate): SQL +=' callDate = %(startDate)s' Currenly I write this code over and over in PHP programs and I am migrating to python to clean up the code. I always thought this was ugly. I just took a look at the module Ian wrote, it looks interesting, thanks! -Aaron |