I have a table (see below for ddl) which implements a set of locations
for an organization, from the whole organization to shelves in a
particular room. Users never see the primary key, only the NAMEX,
usually as a drop down selection list, sometimes a single selection

The recent discussion in another thread about encoding an entire
materialized path in a single value started me down the following path.
It's common practice on genealogy websites to adopt a numeric encoding
method for family trees of ancestors of a given person.  The tree of a

As it has been written elsewhere, Nested Intervals gradually evolved
into matrix encoding. To summarize, each node of a tree is encoded with
4 integers, which translates into the following schema design:
table MatrixTreeNodes (

Interesting news here:
http://msdn.microsoft.com/netframework/future/linq/
Regards
 Alfredo

hai there,
i am not able to use long data type completely in oracle 8i i am able
to use only 4000 bytes completely,is ther any configuration to be done
before using it.

A little while ago, I remarked that I reluctantly included indexes in the
logical design,  and Marshall asked why.
There's a great case to be made against including indexes in the logical
design, and I suspect Marshall can make that case better than I can.  Let me

I'm in the process of attempting to lay out a general overview of what a
properly set up database would look like for my current employer. My question
is with respect to names.
I seem to see at least 3 types of proper names that are independant

I've never used transition constraints before. How
useful are they? Do many constraints end up being
transition constraints, or are they fairly rare?
Have experience? Share!

My introduction to databases, back in the 1980s, was, in part, by way of
Martin.  I got this description of  multiple views of data: the conceptual,
logical, and physical views.
The conceptual view of data:  the data as seen by the subject matter expert.

I am with a silicon valley, bleeding-edge startup requiring some fancy,
innovative database techniques in order to address its core requirement
- highly frequent, dynamic schema growth driven by end-users, on an
as needed basis. Most of the changes are "adds" versus

I want to describe an object that I've been imagining for a while.  I've
called it the "Janus".
A Janus has two faces.  I can describe each face reasonably simply:  one
face is  an SQL client, the other face is  an object, interacting with other

Assume
1. there is a meaningful (or at least consequential)
difference between:
    toppings([salami, mozarella, onions]).

Assuming domains x in {1,2} and y in {a,b} what is the result of
{(x=1)} <OR> {(y=a)}
? Is it
x y

Every now and then, I come across a IT-project that stores its data in
a generic data model. Such data models basically consist of 4 tables:
Entities, Relations, Attributes and Values. The Entities table contains
a record for each table in the conceptual data model, Attributes a

Does anyone know of any interesting constraint taxonomies?
I am aware of
1) D&D's domain/column/table/database hierarchy, which is
intuitively appealing but I'm not convinced it has much behind it.