13.07.2015 Views

iReport Ultimate Guide - Nimsoft Library

iReport Ultimate Guide - Nimsoft Library

iReport Ultimate Guide - Nimsoft Library

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Data Sources and Query ExecutersFigure 11-38 Export connection and data source definitionsIf a duplicated data source name is found during the import, <strong>iReport</strong> will append a number to the imported data source name,as shown in Figure 11-39.Figure 11-39 Imported data source (Empty data source is duplicated)11.8 Creating Custom Languages and Query ExecutersOne of the most exciting improvements since JasperReports 1.2.6 is the ability to use custom languages inside <strong>iReport</strong> toperform a query. Currently, UR provides native support for the following query languages: SQL, HQL, XPath,EJBQL, and MDX.A custom language is a query language that is not supported natively by UR. The language will be used by thereport query by which data to print will be selected. A custom language is tied to a query executer, which is an object that willbe used by UR to process the custom query and get data as a JRDataSource object.In order to use a new language, you have to register it. This can be done from the Options dialog in the Query Executers tab(see Figure 11-40).209

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!