Re: Operationalize orthogonality

From: Erwin <e.smout_at_myonline.be>
Date: 29 May 2006 03:19:15 -0700
Message-ID: <1148897955.538576.154420_at_j33g2000cwa.googlegroups.com>

Translate an external representation of a value to an internal one (and ring a bell if an external representation turns out to be "not a valid value of this type"), the structure of which is comprehensible to the dbms's storage engine ???
Translate an internal representation of a value to an external one (maybe text-like, maybe a format defined by some host language) ??? Define the API that the operator implementations must adhere to ???

I think it 's that kind of stuff. That is to say : if by "type system", you understand the same thing as I do. Received on Mon May 29 2006 - 12:19:15 CEST

This message: [ Message body ]
Next message: Erwin: "Re: Why all the max length constraints?"
Previous message: x: "Re: OT Bull-fight avoidance (was: Why all the max length constraints?)"
In reply to: mAsterdam: "Operationalize orthogonality"
Next in thread: x: "Re: Operationalize orthogonality"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message