Burak Emir wrote:
>
> With XQJ, the aim is to provide an interface to XQuery for programmers.
> Programmers like interoperability, they do not want to care whether the
> server has 8 registers or 32 and what the endianness is. They like to
> parse COBOL or ABAP query in ASCII and turn it into an XQuery (parse
> tree). They like to have a single place where column (or element) names
> are kept. They like to encapsulate everything database specific in a
> high-level API, so *their* users don't even think of XML and queries
> anymore. All this is made easy with a tree-like interface.
Static query analysis, compile-time type checking, etc. do not preclude coding
queries as strings -- look at the SQLJ API.
