|
From: eric m. <emi...@gm...> - 2007-03-21 22:32:55
|
On 3/21/07, Robert Manning <rob...@gm...> wrote: > > On 3/21/07, eric millham <emi...@gm...> wrote: > > Hi, I see the alias properties function to copy down all the schema's > and > > then refine which schema's I want tables loaded for. This is nice. But, > I > > have a little twist on that, I need to create a static list of schema's > to > > load tables for and have as a default to not load tables for other > schema's. > > This is because we have literally hundreds of transitory schema's that > show > > up with random names and then disappear. Squirrel takes forever to start > up > > on this database. I do need the metadata for the static schema's and > tables > > though. Ideas? > > 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 Hi Rob, I did not understand the function then. It appeared to me that this was a way to exclude specific schema's. But, I didn't get that a new schema, not in the schema select list, would, by default, not be included. I suppose that since there was also a way to specifically include schema's that should have been my clue that only the included schema's would be loaded from then on. Anyway, good news, thanks. 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. |
