[Chandler-dev] [Sum] The Great Architecture Discussion of 2007
Andi Vajda
vajda at osafoundation.org
Tue Oct 9 16:12:38 PDT 2007
On Tue, 9 Oct 2007, Phillip J. Eby wrote:
> 1. application-level code meddling in storage-level details
Could you give some examples ?
> 2. lack of sufficient domain-specific query APIs
Again, please give an example of what you'd like ?
> 3. no indirection between the application's logical schema and its physical
> storage schema
Seems incorrect. I can change the physical storage schema (core schema or even
repo format) without affecting app code. Or am I misunderstanding something ?
> 4. implementing a generic database inside another generic database
That was the goal, originally. Not to have a hard compiled app against a hard
compiled relational schema. If Chandler is to become a hard compiled
application with a static schema, where all data types have to be determined
in advance, then of course, the chandler repository is overkill and can be
replaced by some specifically optimized, domain-specific, schema.
> 5. implementing generic indexes inside of generic indexes
How so ? What are you thinking about ?
Andi..
More information about the chandler-dev
mailing list