A few years ago, the dbdebunk.com site had an exchange at:
http://www.dbdebunk.com/page/page/1396086.htm
which I found very interesting.  I haven't seen that exchange mentioned
much here but I think it is likely very important.  The three

I'm still on the same view updating theme but I thought I'd make a new
subject so as not to sully D&D's stuff with some of  my asides under the
other thread.  I'm usually guilty, on purpose, of aside-overload because
some of the smarter people here often clarify my misunderstandings ...

Hi, I'm designing a simple database to help out a co-worker.  There
are some questions I think are worth asking this individual before I
go any further, but I'd like some feedback on the approach I've taken
so far.   This database is intended to assist in managing massive

A some know and might be interested into, I am currently building a db
core and currently trying to move forward onto giving it a compiler to
allow programmers a practical access to relation operations and
separating relation presentation...

I'm using sqlite.
I need a DB that contains:
- a set of general tables
- a variable number of sets of users tables.

My group is working to create a new set of Db standards as we embark
upon redesigning our new web app backend db. The other architect wants
every table/column/variable name to be unabbreviated and as
descriptive as possible. This of course leads to long and ungainly