Issue Details (XML | Word | Printable)

Key: CORE-1117
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dmitry Yemanov
Reporter: Markus Woehling
Votes: 11
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Remove or extend limit of command text length (64K)

Created: 30/Jan/07 03:11 PM   Updated: 14/Feb/14 05:06 AM
Component/s: Engine
Affects Version/s: 2.0.0
Fix Version/s: 3.0 Alpha 1

Time Tracking:
Not Specified

Environment: Windows
Issue Links:
Duplicate
 


 Description  « Hide
A command text (I tried it with a dynamic SELECT statment) can't be longer then 65535 bytes. The parser seems to refill the first bytes of the buffer after this limit is reached (a command of length 65536 produces an error in line 1, column 1).

Sample SELECT statement: SELECT NULL, NULL, ...., NULL FROM <AnyTable>

It would be great if you can remove or extend this limit (maybe to 16M like MSSQL and Oracle)

Firebird 2.0 embedded was our first choice for an embedded solution besides MSSQL and Oracle, but this limitation prevents us from using firebird :-(
We are using an OR-mapping solution that produces quite long sql statements (if the query is complex ;-)

 All   Comments   Work Log   Change History   Version Control   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Holger Klemt added a comment - 25/Oct/10 07:47 PM
i second this old requirement, especially also for procedures and triggers, it would be very useful to remove this limit, since i already often have problems with this limit

Holger
www.ibexpert.com

Marcelo Fortes added a comment - 26/Feb/13 05:27 AM
Its really, really very annoying limitation !

Tim Kelly added a comment - 14/Feb/14 02:05 AM
I just hit this limit in Firebird v2. This is a bit of a showstopper for me. Would backporting the fix be that difficult to version 2?

Dmitry Yemanov added a comment - 14/Feb/14 05:06 AM
Tim, this is absolutely impossible. Moreover, even with v3 it won't work automagically upon upgrade, it must be supported by the connectivity layers.