Hi, sqlite team, i meant to address this directly to Richard a couple weeks back, but we got carried away with other topics...
In the Fossil SCM and (by extension) libfossil, we juggle 1-3 db handles for the config, checkout, and repo dbs. The first db which gets opened (it's use-case dependent!) becomes the "main" db and the others get attached with a well-defined name. The problem is, an application does not (cannot) necessarily know which order the dbs were opened, so it doesn't really know if "main" is the repo db, the checkout db, or the config db. Normally this is not a problem because we have no table name collisions which would require full qualification. However, it becomes exceedingly tedious when, for example, a client app wants to install a new table in (e.g.) the repo db. He doesn't know if he needs to use "create table main.foo..." or "... repo.foo...". He can, thanks to C APIs, fetch this info, but it intrudes quite a lot on the client code. (@Richard: this hasn't come up in fossil(1) yet only because client's don't have a way to do it, but it has come up in fossil(3) while experimenting with client-installed extensions.) My request is the ability to alias or rename the db (not table) names, so that i can tell libfossil that, e.g., "repo" is always the repo db, even if it's really (also) "main". Perhaps a pragma: pragma table_alias oldname aliasname or pragma table_rename oldname newname either one would suit my purposes just fine. :-? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
