JasperReports Data Truncation

[carmi_cd]

I designed JasperReports using IReports..

my problem is one of data from a field in the

database was trucated.

It seems that JasperReports is truncating

the field value when it reached to more than

1024 characters. What should i do to solve

this truncation problem?

 

I already set to true the Stretch with overflow property.

 

thanks in advance for your help

[kschmitte]

Hello All,

 

for me it is the same - I can't get more than 1024 characters in my textField - although the filed is designed to be much bigger and "Stretch with overflow" is set to true.

I checked if setting the styledText Attribute would help - no change in behaviour.

In the xml of the report (generated from IReport 2.0.2) I could also not see any restriction.

 

 

It seems as if this forum has nop answers yet (see e.g. http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=&func=view&catid=9&id=37284#37284).

 

Is this by design? Or is this a bug?

Is there a way to work around this limitation?

 

The report should be shown in JasperServer - maybe I can set here another limit?

 

 

Thanks for your help!

 

Kai Schmitte

[lucianc]

JasperReports does not truncate values retrieved from the DB. Maybe the DB engine or the JDBC driver does this?

 

How can this behaviour be reproduced?

 

Regards,

Lucian

[kschmitte]

Hello lucianc,

 

thanks for the reply.

 

The SQL works when being executed in a simple SQL Tool. The original program (php) does read/write without issues.

 

 

Unfortunatly I cannot provide you with the table (to try to reproduce it in your lab), as the data is company confidential.

 

I will try to build a sample table when I'm back from my business trip next week.

 

Gruss,

 

Kai

[kschmitte]

OK - shame on me.

It seems to be the GRPUP_CONCAT() in my SQL which I use to concatenate the contents of differnent rows which cuts the content at 1024 chars.

Unfortunatly it's hard to see in the returned data from the SQL that there is something missing...

 

Sorry for any inconvenience.

 

Kai Schmitte