Now we have assymetric way to choose object that should be added to the context:
1) SchemaNameFilter - is the string with one schema
2) TableFilterInclude - string with regexp
The typical scenario with large database requires including different objects in different schemas to the db context. So we can't use just SchemaNameFilter. But the objects in the different schemas may have the same name, so we can't use TableFilterInclude.
It would be more convinient to have something combined:
{{ schema_name1_regex, table_name1_regex },{ schema_name2_regex, table_name2_regex }}
Honestly for the my scenario more convinient to have simple struct like
{
{ schema_name1, tables = { table_name1, table_name2}, procs = {proc_name1, proc_name2}},
{ schema_name2, tables = { table_name2, table_name3}, views = {view_name1,...},... },
...
}
1) SchemaNameFilter - is the string with one schema
2) TableFilterInclude - string with regexp
The typical scenario with large database requires including different objects in different schemas to the db context. So we can't use just SchemaNameFilter. But the objects in the different schemas may have the same name, so we can't use TableFilterInclude.
It would be more convinient to have something combined:
{{ schema_name1_regex, table_name1_regex },{ schema_name2_regex, table_name2_regex }}
Honestly for the my scenario more convinient to have simple struct like
{
{ schema_name1, tables = { table_name1, table_name2}, procs = {proc_name1, proc_name2}},
{ schema_name2, tables = { table_name2, table_name3}, views = {view_name1,...},... },
...
}