Importing database schemas into subpackages

[MaXyM]

Hello everybody.
Recently while gathering new experience of importing database EA's feature, I found - I believe - a bug. I decided to ask for that on this forum before I report it to official support.

EA imports all db objects into packages named after object types. This way all tables are imported into Tables package. Until we have tables from single db schema and we are ok these are located in single package - everything works as expected. But our database contains hundreds of tables divided into few dozens of schemas. Imagine all those tables in Project browser tree, in single package sorted by table name... In fact impossible to manage.

Issue 1: In project browser, an item which represents database table is not prefixed by schema name (like available on diagram). This way it's very hard to find all tables of particular schema in Project browser. It affects user experience significantly. Maybe there is some feature/switch to enables db schema names in Browser. I haven't found one.

Issue 2: while already imported tables are moved to subpackages (for example Tables/MySchema/) and we proceeding with importing another tables, EA is not able to create relationship between new tables and already imported ones. I could had have even consider it as a feature (even if not handy, though) but I've found one thing which proves it must be a bug. In DatabaseBuilder, function "Show differences" shows missing relationships and moreover, it gives option to sync it with db. Unfortunately attempt of import does nothing at all. I checked out, that moving parent table (of relationship) from subpackage to Tables package, makes sync with db working again. So import/sync works but result depends on where table objects are located in project tree.

Do you have some experience with RE of databases? Can you confirm this issue appear to all DBMS (I found it while working with postgresql)?

With regards.