Nevermind. I was being overzealous in verifying the format of the event text. It seems that long
sql statements generate -multiple- events to cover the whole length. It'll be a mess to handle, but
at least the whole thing is there in one way or another.

-Philip

---------- Original Message -----------
From: "unordained" <unordained_00@...>
To: firebird-support@yahoogroups.com
Sent: Tue, 21 Dec 2004 16:55:13 -0700
Subject: [firebird-support] TIBSqlMonitor

> I'm trying to use TIBSqlMonitor as a centralized benchmarking and slowness (delay from
> request to first response row)-detecting component for our already-large project. Not all
> of our SQL runs through our own functions, particularly anything related to QR. Sadly, it
> seems whoever coded TIBSqlMonitor (Jeff Overcash?) decided that 1000 or so characters
> would be plenty for any SQL, which isn't the case (and of course it's a const, so I don't
> think I can just derive and override the value.) Without the full SQL, it's hard to track
> down the source of the call, and therefore what SQL or indices might need fixing. Any
> suggestions? I have the sourcecode, so I can technically recode the darn thing to not have
> such a limit, but my pascal's a bit rusty and I was hoping maybe someone else had already
> done so.
>
> -Philip
>
> ------------------------ Yahoo! Groups Sponsor --------------------~-->
> $4.98 domain names from Yahoo!. Register anything.
> http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/67folB/TM
> --------------------------------------------------------------------~->
>
> Yahoo! Groups Links
>
>
>

------- End of Original Message -------