Ewww, sub-selects. Not a very efficient use of the DB, is it? I was under the impression that it's just as fast (with MySQL at least) to just do the sub-select yourself in the code instead of relying on the database to do it.
Dan Carl wrote: It depends on who is going to access the database. Depending on the usage model, I might even be inclined to use sqlite for a database of this size. It is faster than MySQL as long as it doesn't need to be accessed by very many users simultaneously, is fully ACID compliant, and offers some useful features that MySQL doesn't currently support (at least in its stable releases), such as subselects. Carl ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
