Yeah, i am thinking just names that the SDE approach is the best way to go.
I know the names are ugly but at least in the geoserver case the user can
set a different name if they want to.
I guess the only issue is code (mostly in the dialect) that takes schema as
a parameter. I guess the datastore
Zitat von Andrea Aime :
> On Thu, Jan 12, 2012 at 4:44 PM, wrote:
>
>> Oh yes, I know the problem. Creating a db2 data store without a schema
>> lists a ton of tables including the whole system catalog.
>>
>
> You know you can setup table name filters in the sql dialect?
> That's how we hide most
On Thu, Jan 12, 2012 at 4:44 PM, wrote:
> Oh yes, I know the problem. Creating a db2 data store without a schema
> lists a ton of tables including the whole system catalog.
>
You know you can setup table name filters in the sql dialect?
That's how we hide most of the system tables in Oracle for
Oh yes, I know the problem. Creating a db2 data store without a schema
lists a ton of tables including the whole system catalog.
I would prefer a more precise solution, but I am not sure if it is possible.
1) We always use schema.table, because this it the unique name,
comparable to a java cl
Hi,
I'm looking into some options to have a JDBCDataStore work against multiple
schemas at the same time without troubles.
Right now the code works two ways:
- if you specify a schema during the store setup, we work against tables of
that
schema and we're fine
- if you don't the list of possibl
