Daniel_Work@... wrote:

>
> SQL Statement Dependency Mapping
>
> I had an idea for a tool / API extension for obtaining the schema
> dependencies of a DML statement.

In fact, I think it is possible to obtain the desired result (the list
of dependants of a DML) with a few querys.
Think that you can do a query like

select * from rdb$dependencies where rdb$dependent="tablename"
or
select * from rdb$dependencies where rdb$dependent=" SP name "

You can do a selectable SP that, having a SP name as parameter, extract
all the dependencies, an can be recursive!

So, I think there's no need for new API calls, just do some querys.

Collecting the result of this SP to do a graph of dependencies, etc. is
not an issue here, I think.

Catch I your idea?

Regards

Adrián

>
> My theory goes like this, Interbase's SQL query engine would already be
> able to determine tables, columns, etc that a statement requires for
> execution.
>
> If these requirements could some how be extracted and dumped into a file
> together with the requirements of other SQL statements an overall schema
> dependency map for an application could be built.
>
> For example I could see a Delphi expert scanning through the forms in a
> project extracting the SQL from queries for dependency mapping.
>
> Does this sound like a feasible/usefully idea?
>
> Would it be a new tool or an extra set of API calls?
>
> PS I haven't been following the list too closely so if this isn't a new
> idea please be kind ;-)
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com