Re: QRe: sql parser for oracle 9i

The only thing I can think of that comes close is to reverse engineer into Designer and then use the standard reports. As designer is built on a fairly impressive meta model, which I think at one time was just 2 tables, the info should be accessible there.

Other than that I dont know if PRO*C / OCI would provide such info or possible jdbc ?

I'd be interested to hear if you get to a solution.

Cheers

Mike

In message <cHq6a.11518$V6.15593_at_news.indigo.ie>, Telemachus <telemachus_at_ulysseswillreturn.net> writes
>Don't Quest software (the TOADies) make something along these lines ?
>"christian kasper" <christian_at_kasper.ws> wrote in message
>news:329aa663.0302240554.395c6bdb_at_posting.google.com...
>> Mike <mike_at_nospam.demon.co.uk> wrote in message
>news:<HxTQltBw0jV+Ewbd_at_ntlworld.com>...
>> > In message <329aa663.0302210615.1a65aa42_at_posting.google.com>, christian
>> > kasper <christian_at_kasper.ws> writes
>> > >hello,
>> > >
>> > >i need a sql parser for oracle 9i.
>> > >Don
>> > >do you now a company or a open software project or something, where i
>can get
>> > >the parser ?
>> > >
>> > >thank you.
>> > >
>> > >christian kasper
>> >
>> > In what context ?
>> >
>> > If you need to validate sql statements then the built in package
>> > dbms_sql will suffice.
>> >
>> > Cheers
>>
>>
>> Thank you fro your help.
>>
>> You are right, the kontext of my parsing problem is important.
>>
>> I have a application with thousands of sql statements in pl/sql
>> scripts, in triggers, in pro*c programs, in shell scripts ...
>>
>> My work in the project is to develop a scanner for
>> insert/update/select/delete statements to describe the r/w access per
>> procedure/trigger/function/script on tables/views. The output of the
>> scanner is a html file that describes the relationship between
>> procedure/trigger/function/script and r/w access on tables/views for
>> documentation purposes.
>>
>> My question is, do you know a parser, who give me the names of
>> tables/views in selects/insert/update/delete statements. The parser
>> must know the syntax from oracle 9i.
>>
>> Thank you
>>
>> Christian Kasper
>
>

-- 
Mike Cox