schneider.luke Posted January 29, 2014 Share Posted January 29, 2014 Odd issue here:Just installed Jaspersoft Studio 5.5 (OS X Mavericks)Connected to external mysql database just fineEntered a query I've been using for months in iReport without issueStudio query editor shows syntax errors in several places (e.g., mismatched input, mismatched character)Can't preview dataCan't preview report (java.lang.IllegalArgumentException: Null 'dataset' argument)Anybody know why this query would suddenly stop working on Studio 5.5? Link to comment Share on other sites More sharing options...
marianol Posted January 29, 2014 Share Posted January 29, 2014 Have you selected a proper data adapter for your report? Remember that studio uses data adapters (instead of datasources) and the report remembers the specific data adapter that you havce chosen. Creating the data adapter does not means that Studio will use it for all the reports you open (like iReport did). In Studio each report remembers the data adapter you have selected previously for that report when running.If you imported the report from iReport; Studio will have no data adapter assigend to that report and you have to pick one before you can run your query. Link to comment Share on other sites More sharing options...
schneider.luke Posted January 29, 2014 Author Share Posted January 29, 2014 Thanks, Marianol. I have selected the proper data adapter. It's as if the acceptable mysql syntax has just changed between the two products (iReport and Studio). When I run the identical query in Sequel Pro and iReports I get a normal dataset returned. The error I get when I try to "read fields" in Jaspersoft is a "check your SQL syntax . . ." . The red "X" marks in the query editor indicate mismatched inputs and missing EOF when I mouseover them. Link to comment Share on other sites More sharing options...
jimj Posted May 18, 2016 Share Posted May 18, 2016 I used a query generated by Toad and tried to add where with a parameter and it gave an EOF error in the query window. I moved it above the group and order clauses and it worked. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now