> >> That means that external tables has to be defined in the database
> >> explicitly. As to the explicit queries - if they are used often - people
> >> can define them as views (finally - as selectable procedures, add syntax
> >> extension to CREATE PROCEDURE statement).
> >
> > This way is used by ASA. I very very not like it. It is hard in use and require many
> > efforts from end-user.
>
> Can you provide a list of problems with this solution? Why is it hard to
> use and what exactly efforts are required from end-user (not database
> developer/administrator)?

If i had a provider connected to a database with dozens of tables, and
ocasionally i need to query some of these tables (in some reports, for
example), it will not be pratical to create on local table for each
remote table. The thing gets worse if i have a external reporting
tool, and some end users are able to create their own queries.

I would preffer:

select * from provider@table1 where ....

Rather than:

create table prov_table1 (
....
)

select * from prov_table where ...