On 11 janv. 2011, at 01:54, Richard Hipp wrote: > > So the question to you, gentle reader, is should we make this change, and > break backwards compatibility, albeit in a very obscure way, or should we be > hard-nosed and force hundreds or perhaps thousands of smartphone application > developers fix their programs? > > --
I have very little sympathy for poorly written apps, and for their developers. Accommodating them by increasing the complexity of SQLite may seem the right investment in the short term, but is almost certainly a losing proposition in the long term (as your question here shows already). I vote for keeping the API clean. The lazy developers will have to fix their code or be driven out of the market (for the benefit of everybody). Perhaps make the topic more visible in the documentation. Nothing more. Don't be accommodationist. You stand to lose more than to gain. Jean-Denis _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
