Can't get past query design

[mzenns]

I just downloaded iReport 4.0.2 (due to a hard drive crash that wiped out my previous version and all my saved reports).  I use the Query Designer to design the following query:

SELECT
     servs_provices_accounts.`id` AS servs_provices_accounts_id,
     servs_provices_accounts.`servs_provided_services_ida` AS servs_provices_accounts_servs_provided_services_ida,
     servs_provices_accounts.`accounts_idb` AS servs_provices_accounts_accounts_idb,
     accounts.`id` AS accounts_id,
     servs_provided_services.`id` AS servs_provided_services_id,
     accounts.`name` AS accounts_name,
     accounts.`account_type` AS accounts_account_type,
     servs_provided_services.`loc_address` AS servs_provided_services_loc_address,
     servs_provided_services.`loc_address_city` AS servs_provided_services_loc_address_city,
     servs_provided_services.`loc_address_state` AS servs_provided_services_loc_address_state
FROM
     `accounts` accounts,
     `servs_provided_services` servs_provided_services,
     `servs_provices_accounts` servs_provices_accounts
WHERE
     accounts.`account_type` = "Customer"

 

and when I try to go to the next step, I get this error:

Query error
 

Message:
    net.sf.jasperreports.engine.JRException: Java heap space
Level:
    SEVERE
Stack Trace:
Java heap space
    com.jaspersoft.ireport.designer.data.fieldsproviders.SQLFieldsProvider.getFields(SQLFieldsProvider.java:441)
    com.jaspersoft.ireport.designer.connection.JDBCConnection.readFields(JDBCConnection.java:470)
    com.jaspersoft.ireport.designer.wizards.ConnectionSelectionWizardPanel.validate(ConnectionSelectionWizardPanel.java:146)
    org.openide.WizardDescriptor$7.run(WizardDescriptor.java:1357)
    org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572)
    org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)

 

How do I get to the next step?
 

BTW, this happens with every query I try.

Post Edited by mzenns at 05/17/2011 16:35

[despec]

Well, the thing that sticks out to me is that your query results in a cartesian table because you have nothing joining the tables together. That may be causing the server to timeout depending on the size of these tables.

 

David