Joost van der Sluis wrote:
I am a firm proponent of putting a unified mechanism for a) and c) in
TSQLQuery/TSQLConnection, and have, in fact, a patch ready for this
(it implements a simple event mechanism for the log).
That's a no-brainer. It could als use TCustomApplication.Log, if
Customapplication is assigned. Or, add events before and after an
statement is prepared, executed or unprepared. (And when data is
fetched)
But should we add this code in the connection-objects for each db-type,
or in the code in the sqldb unit?
Or maybe both? Certainly in the case of PostgreSQL both have handles
provided by the underlying client library, those handles are useful for
different things, hence it might be desirable to hook either or both
even if in some cases there was duplication of output.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
