Title:
INSERT query on Oracle database with maxrows attribute on cfquery tag crashes
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Dave Merrill / Dave Merrill (Dave Merrill)
Created: 12/18/2012
Components: Database
Versions: 10.0
Failure Type: Crash
Found In Build/Fixed In Build: Final / 286644
Priority/Frequency: Critical / Some users will encounter
Locale/System: English / Windows 7 SP1 64-bit
Vote Count: 0
Problem Description: Running a SQL INSERT query against an Oracle database with a maxrows attribute on the cfquery tag crashes.
Steps to Reproduce:
<cfquery name="qry" datasource="SomeOracleDSN" maxrows="SomeNumber">INSERT INTO SomeTable (...) VALUES (...)</cfquery>
Same result with Oracle 10g and 11g.
Actual Result: Crash, stack trace provided in attachment.
Expected Result: No crash (:-)
Any Workarounds: Remove maxrows attribute, use a different database, don't run INSERT query.
It may seem like removing maxrows on inserts is so easy that this isn't worth fixing, but generic query infrastructure shouldn't have to parse the SQL to figure out if it's an INSERT.
Reported by two users on different machines, different Oracle versions.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3431423
External Customer Info:
External Company:
External Customer Name: dmerrill
External Customer Email:
External Test Config: My Hardware and Environment details: Sony i7 laptop running Windows 7 Pro SP1 64-bit.
Attachments:
- December 19, 2012 00:00:00: 1_cf10-crash.txt
Comments: