This XDb2 example (www.xdb2.com/Example/Ex109.asp) represents the
following things with variable number of properties and values:
wig1's color is red.
wig2's color is red, green AND texture is soft AND material is nylon.

Say I have a sales history table that has the following fields: custid,
invoicedate, prodid, quantity, cost, sale.  And that I want to select
sales records where invoicedate is between 5/1/04 and 8/31/04 and where
these are new sales for each customer, meaning that the customer ...

The following script models members of a baseball team. The final
data, which is normalized to atomic symbols, can be seen in tables and
trees at www.xdb2.com/Example/Ex102.asp
create *address cls thing.

Hello can anyone explain what ghost update does in  a concurrent
transaction? What I haven't understood is suppose an integrity
constraint exists which says x+y+z = 1000 and concurrent transaction
table below:

I have been struggeling with this question for a while.
Let us say I have Part# and it has very large number of flexible
attributes defined by the user, such as color, width, height, etc...
Depending on Part number, these attributes may change.

I have two tables populated during the use of an application to log
user events and application states.  They are named "EventTable" and
"StateTable" and the structures follow:
EventTable:

Can any one help me to build a data model for storing a "SQL Where Clause".
Thanks in advance,
Raj

I have a question about how is Database software constructed ?
Say Oracle/Sybase etc database software, how are they programmed ? ie
how is data actually stored in tables, or actually in files ?

Please forgive me if this question is naive/asked every other
week (to date I've been unable to find an answer on Google.)
My question: is there any reason why a purely relational database
interface, in the "Third Manifesto" sense of, say, Tutorial D,

I was browsing through the archives and found this gem, which remains
unanswered. I for one would very much like to know what you are
referring to, and why the solutions proposed in the book are "weird"

I've got two tables (master and detail) with a many-to-one
relationship between them.  I want to to perform a query which will
join them but ONLY the first detail record for each master i.e.
Pseudo definitions are:

Over the years, I've tried several different relational database schemes for
tracking personal and professional information, and in every instance have been
frustrated with the results.
The biggest problem seems to lie in identifying entities, or 'things.'  For