> -----Original Message----- > From: Cory Nelson [mailto:[EMAIL PROTECTED] > Sent: Saturday, November 05, 2005 11:40 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Request for comment: Proposed SQLite API changes
> > *I* know that, and *you* know that, but the idea is to > minimize the impact > > of inefficient code. This is somewhat akin to the ol' += > string concat > > operator ... so many people use it that you can't throw it > out the window as > > inefficient -- but you CAN change your underpinnings to > minimize the impact. > > As a wrapper writer I can't control how people code -- in > my case I am bound > > by the ADO.NET 2.0 architecture and have a standard that I > cannot deviate > > from. > > Hmm... no. It is not the job of the author to optimize for improper > use of something. If you have so many ignorant users, perhaps you > need to re-think your documentation. First, there's a difference between improper and inefficient. String concatenation using a += operator is not improper, but it can be inefficient if the string class doesn't use its buffer wisely. Likewise building a SQL string each time and executing it isn't improper, but depending on what it is, it can be inefficient. As for the documentation, tell that to Microsoft. I didn't write ADO.NET. I have an entire section of my helpfile dedicated to educating users about the wonders of paramerized queries and transactions, but I can only lead the horse to water. Robert
