> Actually, my expectation is the other way. I'm continually surprised > by posts on this list that people expect to be able to use SQLite with > no external programming at all. I often see complicated compound JOIN > and sub-SELECT SQL commands here which can be replaced by four lines in > any programming language, yielding faster simpler code which would be > easier to document and debug.
I'm not surprised at all. I happen to be a programmer, so this doesn't cause me any problem, and, in fact, I'm excited I can do it this way. But, you do have a fair number of people that come into this from environments where you can't necessarily combine standard programming and SQL. For instance, I come from an MSSQL world, and while they now support a very nice C# environment within the SQL server to do both SQL and algorithmic programming, before that, it often took too much time to extract data from a remote server, manipulate it, and then send back changes. At least, it did in my environment. So, we learned to use the minimal algorithmic abilities (in this case, T-SQL). Complex joins, subselects, T-SQL whiles, and cursors where the order of the day. Even though the majority of my development is standard programming, my mind still hitched on a message last week or so on this forum that told some poster that there was no "if" statement. I had a momentary panic until I remembered that I could just write regular code. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
