On Wed, 21 Apr 2004 [EMAIL PROTECTED] wrote:
>
>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!!!
If a new revision of some app requires updated tables, there are
invariably bigger problems than changing the schema.
Changing the schema is the easy bit, just write a script to dump the old
data, recreate the table, and restore the data from the dump.
The only troublesome schema updates in my experience (which to be fair is
not massive) is where the data model has fundamentally changed, and ALTER
TABLE ain't gonna help you with that.
>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.
Agreed.
>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...
I'm not sure about anyone else, but I've used SQLite mainly as a data
store. I'm working on a project which will have trigger based callbacks to
C code for cache invalidation, but that's about it.
Whatever, you have the source, so scratch that itch...
Christian
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
