Please don't top-post and include everything that went before. On 11 Jan 2011, at 17:10, Scott A Mintz wrote:
> There's the issue of "this is what I meant" vs. "this is what I did." When > you have a couple hundred customer's, changing the code is painful but > doable. When you have a couple million customer's, then what is "out > there" is the "true" API and must be kept around. If that were generally true no-one would ever change (or even add) anything in any software library product. The problem here is that there are two mutually incompatible versions out there already, pre-3.6.23.1 which generates SQLITE_MISUSE in many cases and post-3.6.23.1 which generates SQLITE_MISUSE practically never. Introducing a third incompatible version (as proposed to start this thread) which generates SQLITE_MISUSE with a frequency between the two is unlikely to make things better; if anything it will make things worse. If we knew that no-one had shipped dynamic libraries for a version >=3.6.23.1 and <now it would invalidate that argument; unfortunately 3.7.2 shipped in Ubuntu Maverick and 3.6.23.1 shipped in a maintenance update for Fedora Core 14. So lots of people already have both behaviours in the wild. Best Regards, Phil Willoughby -- Managing Director, StrawberryCat Limited StrawberryCat Limited is registered in England and Wales with Company No. 7234809. The registered office address of StrawberryCat Limited is: 107 Morgan Le Fay Drive Eastleigh SO53 4JH _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
