Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!usc!bloom-beacon!eru!luth!sunic!mcsun!tuvie!edvvie!eliza!johnny
From: johnny@edvvie.at (Johann Schweigl)
Newsgroups: comp.databases
Subject: ORACLE PRO*C tracing tool
Keywords: ORACLE SQL PRO*C C
Message-ID: <173@eliza.edvvie.at>
Date: 8 Oct 89 08:35:01 GMT
Organization: Edv GesmbH, Austria/Europa
Lines: 16

I'm currently writing a tracing tool for PRO*C programs, that collects
timing information for every SQL statement executed automatically.
The modules that collect data from the PRO*C precompiler are 
ready (thanks to Jonathan Creighton).
If anybody of you is interested, please answer a simple question:
What would be the more appreciated way of recording the data
  -  into a set of ORACLE tables on a per-user base, requiring the user
     to run a report after the execution of one (or more) traced programs
  -  into a set of global trace tables
  -  to stderr
Email, please
-- 
This does not reflect the   | Johann  Schweigl | DOS?
opinions of my employer.    | johnny@edvvie.at | Kind of complicated
I am busy enough by talking |                  | bootstrap loader ...
about my own ...            |   EDVG  Vienna   |