Re: Nearest Common Ancestor Report (XDb1's $1000 Challenge)
Date: 18 May 2004 13:01:31 -0700
Message-ID: <4b45d3ad.0405181201.5d505bda_at_posting.google.com>
> the schema should be strictly seperate from the data
In XDb1's data model there is no separation between data and schema at the db level, however the app logic can choose to make those distinctions if needed.
> and the datatype of the data should be known.
In XDb1's data model, "data type" is simply an additional classification of a thing. If it needs to be known, it should be classified as such (ie. 35 isa integer).
> And this is exactly the reason why I'd never use XDb1 for serious work,
> unless I encounter a problem area where the advantages of allowing untyped
> data outweigh the disadvantages.
I think, I finally understand what you are saying. In the example, since 35 was only classified as an age, it appears to be "untyped". The example was simple. 35 can also be classified as an integer. Each thing in XDb1 can have multiple classes, one of which can function similar to its "data type". Received on Tue May 18 2004 - 22:01:31 CEST