Re: object list and schema filtering

On 3/21/07, eric millham <emillham@xxxxxxxxx> wrote:
> > I don't think I quite understand what you mean.  If you have a list of
> > tables (that doesn't change) then create an alias and configure only
> > those schemas to be loaded.  The list of included schemas is all that
> > matters and is all that will be loaded - regardless of other schemas
> > that are created and dropped.  Your problem seems to be a perfect fit
> > for the use of Alias properties.  I must be missing something.
> >
> > Rob
>
>

<snip>

> Does your comment that the
> "list of tables that does not change" mean that if a new table is added to
> an included schema that it will not show up? Hope not.

Sorry, I meant schemas.  If you configure alias properties to load
tables for specific schemas, only these will be loaded into the object
tree when you connect.  If you then go back into alias properties and
hit the "connect database to refresh Schema table ", the new schema(s)
will appear in the list as "don't load".  You can then add the objects
from those new schemas as well as any others to be loaded if that is
your desire.

Rob

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV