On 24-11-2013 19:15, Dmitry Yemanov (JIRA) wrote: > > [ > http://tracker.firebirdsql.org/browse/CORE-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27380#action_27380 > ] > > Dmitry Yemanov commented on CORE-3559: > -------------------------------------- > > At the protocol layer, messages are passed as CSTRING with cstr_length > transferred using xdr_short. And the fact that shorts are actually transfered > as longs doesn't completely fix the problem due to possible signed/unsigned > issues when different expecations are used (e.g. 60K transferred as signed > long should not become negative). But the wire protocol is not the only > problem, the public API definitions also use explicit 16-bit lengths for SQL > strings / BLR lengths / message lengths / etc, so all applications that use > fbclient are affected. It's not a problem for the new API anymore, but the > engine has no idea what API was used by the client.
I assume that is an artifact of the implementation, could you point me to some code that shows this. If I look at the (wire!) protocol itself, there is no such limitation to the total message length when sending parameters (eg in op_execute2), although there is a limitation per parameter. Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
