It would be very useful to have the "Create Entity Classes From Database" and "Create Persistence Unit" features work
with a database connection without schema definition, so that you can access tables from different schemata with the
same persistence unit. 

Rationale: 
In databases that support schemata you can use them to organize tables according to a "separation of concerns"
paradigma, e.g. if you need to separate or modularize the database. In such cases you often have one schema providing
containing basic information (e.g., application user data) that is relevant all over the application. Beside this, there
are other schemata concerned with narrow, isolated aspects of the app. The data they contain is also mostly isolated,
but needs to reference the user data in the first schema. If you want to persist entities of the second schema, the
persistence manager also needs to know the first schema. 
Or is there some other solution to this problem?
I would be very grateful for any tips and a short note to info@aeonium-systems.de!