The Ingres JDBC driver, iijdbc.jar, has the capability to log the queries that pass through it. This is extremely useful for obtaining query timings as well as working out what goes between an application and the DBMS server. For example, below is a snippet of a trace obtained from Jira:
2008-07-08 10:04:12.319: Ingres-ResultSet[40296].next()
2008-07-08 10:04:12.319: Curs[40296].load()
2008-07-08 10:04:12.319: [...]
Ingres Newsgroup- Re: Ingres Database 9.2 released (yes, 9.2--it's a long story...)
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and UserDays inAustralia - Update
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and UserDays inAustralia - Update
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and UserDays inAustralia - Update
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and UserDays inAustralia - Update
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and User Days inAustralia - Update
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and User Days inAustralia - Update
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and User Days inAustralia - Update
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and User Days inAustralia - Update
- Re: [Info-Ingres] Ingres OpenROAD Code Sprint and User Days inAustralia - Update
- Community Forums
- timestamp/interval trouble oleaka
- Migration from transbase to ingres , using copy bmwael
- Conectivity Problem qfan
- DAOGen Problems gavin.stilgoe@dpi.vic.gov.au
- Export Ingres data to iSeries DB2 markglazener
- OpenRoad 2006 Display Problems PhillipD
- can I connect a Oracle Database paul weinstock
- timestamp/view strangeness oleaka
- Using OpenAPI in C++ schma01
- Timestamp question oleaka