Puneet Kishor wrote: > my guess is because it can be done other ways (see the docs on this > specifically), and the idea is to keep SQLite as simple as possible. The > more "conveniences" that are added to it, the more complicated it will > become.
> Usually, once the database is set, there is little reason to ALTER it... > it all boils down to ROI... I beg to differ concerning the last point. Adding MORE sql commands is not a convenience but rather can save hundreds to thousands of lines of code!!! I have been programming in SQL for over a decade now and it is by far the best programming language in use, even with all its warts mainly because with one SQL statement can do the work of many lines of code. SQLIte is "Lite" mainly because it is designed around a single user/process with file locking on a single database file. I am sure if it was designed for a multi-user/ server with table/page/row locking over multiple files, it would be at least 10 time bigger even if it implemented the same SQL commands. Increasing SQLite DDL capabilities is a must as well as adding more control-flow statements. Yes I like the fantastic low level control I get by using the "c" api calls but 99% of my client solutions can be written completely using SQL only. I think even in its current implementation, SQLite is the best embedded SQL based engine available and I am sure ver 3.0 and beyond will add more enhancements to the SQL commands it supports... ------------------------------------------------------------ This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen. ============================================================
