That's pretty cool. The thing is, I'm actually not looking for a "conn" (connection" of any sort). I'm thinking of database as a container class. Kind of lik

That's pretty cool. The thing is, I'm actually not looking for a "conn" (connection" of any sort). I'm thinking of database as a container class. Kind of like... db = New db db.addTable(colname, list[names], primaryKey) db.addTable(joinTable, foreignKey, colname, list[names]) Map a = db.(select col a, col b from ...) db = nil and so forth... in other words, we're going the opposite direction from database as storage. Instead, we're going to database as something that is as in-memory as a hash (probably more likely to be persisted at some point, but not necessarily). Sometimes, I see classes created that are bending over backward to recreate a bit of sql, and the model and logic really only exist for one purpose - sql-like methods on the data. People rarely write their own list, set or map classes, but often they will essentially recreate a bug-ridden 1/2 of common sql in their app... Anyway, looks like you've been thinking about this for a while, I'll definitely take a look at the link. Thanks for posting it.