Re: Nearest Common Ancestor Report (XDb1's $1000 Challenge)

> Remove types, and nothing prevents your user from entering "banana" as
> John's age.

It is true that RM implementations provide checking for basic types such as integer. Thus if one trys to enter "banana" for age, it couldn't be done (assuming the column is typed as integer). XDb1 does not provide the usual "basic" types/classes, except those needed to boot the db which are thing, relator, symbol and name. Currently the "basic" types/classes have to be created and checked by the user's code.

Now consider the type/class color. It is not a built in type. How can RM implementations prevent the user from entering "banana" (the fruit) for color?

In most RM implemenations, "basic" types are inextricably related to hardware. In XDb1, no type/class (except maybe for the thing class) is implemented in hardware. Instead, they are abstracted in the db. Received on Tue May 18 2004 - 05:52:42 CEST