This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 267222 - SQL Profiler - SQL statement truncated at 1000 characters
Summary: SQL Profiler - SQL statement truncated at 1000 characters
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 8.2
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-20 09:41 UTC by Crydust
Modified: 2016-08-12 11:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Crydust 2016-07-20 09:41:01 UTC
I'm using the SQL Profiler on a project that generates SQL statements of extreme length.

These SQL statements show up in the profiler, but the end is missing.
At first I tought this was only done to show in the table, but Right-click > View SQL Query doesn't show a longer version than the table does.

I would expect upto 64K characters to be shown in the View SQL Query popup.
Comment 1 Tomas Hurka 2016-08-12 11:34:03 UTC
You are right, there is a limit for size of SQL statements. SQL profiler is not sql debugger - our main task is to track from which java code invokes SQL statements and how long it takes to execute it. We can increase current limit, but it can have performance impact on both profiled application and NetBeans itself. I wonder how you came to the conclusion that upto 64K characters should be shown in the View SQL Query popup. Why not 32K or 128K?
Comment 2 Crydust 2016-08-12 11:53:02 UTC
I read somewhere 64K was the maximum length of a sql statement in Oracle. I just thought the 1K limit felt quite short.

(In reply to Tomas Hurka from comment #1)
> You are right, there is a limit for size of SQL statements. SQL profiler is
> not sql debugger - our main task is to track from which java code invokes
> SQL statements and how long it takes to execute it. We can increase current
> limit, but it can have performance impact on both profiled application and
> NetBeans itself. I wonder how you came to the conclusion that upto 64K
> characters should be shown in the View SQL Query popup. Why not 32K or 128K?