Re: Call for an API standard for SQL statements

From: Alfredo Novoa <anovoa_at_ncs.es>
Date: Sun, 24 Oct 2004 04:27:15 +0200
Message-ID: <sn4mn0l2qouc13iup0epag6olh3rfqfm7d_at_4ax.com>


On 22 Oct 2004 22:29:43 -0700, fredrik_bertilsson_at_passagen.se (Fredrik Bertilsson) wrote:

>> You can do the same with a text parser associating the class with an
>> SQL "domain".
>What text parser are you talking about. Please explain.

An SQL parser.

>> >A second extremly useful feature is converting a two-dimensional query
>> >result into a hierachical view. Lets say that we have a query joinin
>> >the tables "Order" and "OrderDetail". My framework returns a list of
>> >"Order" records, but calling the method "getRelatedRecords" on such
>> >instance, will return a list of "OrderDetail" records. This feature is
>> >only possible if the framework has knowledge about wich tables are
>> >participating in the query.
>>
>> You only need to know which are the "master" and "detail" columns.
>I don't follow you here. And still you need to now the columns.

It is very easy to create a hierarchical view from a query. You don't need to know the tables.

>> >A third example is data-aware GUI components. Lets say we want to make
>> >a search panel which takes a query object, builds a GUI and let the
>> >user fill in the parameters. This is of course only possible if we
>> >have have a query object.
>>
>> We can do the same parsing an SQL text statement.
>Indeed, but you using strings will give use the syntax checking problem.

You will have the semantic checking problem anyway.

Regards Received on Sun Oct 24 2004 - 04:27:15 CEST

Original text of this message