Kevin Wilson wrote: > > version 7.5.0.23:64bit:ascii on linux64 (opteron). > > I have 11980 bytes in varchar plus 3 integer output columns in my join > query, I think this is very small considering the data we have to store > and > fetch these days. Error occurs using both the jdbc driver in our reporting > package and in sql_studio. > > removing the two fields it complains about allows the query but the only > problem is that I need both of those columns on the report. > > Why is the output size so small?
Up to now result rows have to fit into pages of 8KB. Therefore those 11980 are too long. Sorry. There are plans to increase the possible result row size. But these are no real short-term-plans, but medium ones you will not be able to wait for. So the only chance I see is to prepare result rows containing some of your needed columns plus the primary key(s) of the corresponding rows in the other join-tables and then do a select ... INTO :param WHERE <primary key column> = :param for the other long column(s) Elke SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
