Common Problems in Database Query

Version

Application Scenario

This document describes the common problems and detection steps in database query.

Problem:

All English in the SQL editing area of the database query page is garbled, as shown in the following figure.

Cause:

As the SQL editing area of the designer is displayed with the specified font by default, garbled characters will be displayed when the specified font is not included in the computer's operating system.

Solution:

You are advised to make sure that the specified display fonts in the SQL editing area are installed in your computer's operating system, otherwise, you need to install the appropriate fonts, and restart FineReport.

1. IOS: The SQL editing area is displayed in any of the three fonts Menlo, Monaco, and Monospaced.

2. Non-iOS: The SQL editing area is displayed in any of the two fonts Consolas and Monospaced.

Note:

 When the above method does not work, you need to restart the designer after placing fonts under jre/lib/fonts in the designer as well.

Problem:

The dataset can be previewed, but there is no data in the template preview.

Error in the log: Not found data columnid

Cause:

When creating a database query, you cannot name the dataset with "." , for example, ds1.1, otherwise no data will be displayed with the error appearing in the log when you preview the template.

Note: 

No preview failures or errors will occur when you create charts with datasets created by this database query.

Solution:

You can solve this problem by renaming the dataset.