back to forum.

Topic: ORACLE SYNONYMS CANT BE ANALYZED

Topic by
tlamatiniisrael

2012-06-25
20:54

ORACLE SYNONYMS CANT BE ANALYZED

HI, IN MY OFFICE THEY LIKE TO USE SYNONYMS FOR ALL; SO WHEN I TRIED TO USE DATACLEANER THE LOG SAIDS THAT ONLY RETRIEVE THE TABLES AND VIEWS OF A SCHEMA, SO IDONT KNOW IF ITS POSIBLE TO CONFIGURE TO READ SYNONYMS TOO, OR NEEDS TO BE IMPLEMENTED.

THANKS IN ADVANCE

Reply by
kasper

2012-06-26
08:42
Why all the caps? Would you also be shouting this to everyone's heads if this was a real life conversation?

Reply by
kasper

2012-06-26
08:58
Anyways, to get to the issue ... You are correct, DC only scans for Tables and Views.

I guess we should add as an option to select which table types to scan for. I've created this issue in our bugtracker to make sure we get it done:

http://eobjects.org/trac/ticket/873

It will be a small fix, but you'll have to wait for the next release or use a nightly build.

Reply by
tlamatiniisrael

2012-06-26
20:31
no shouting just a carelessness of my self...

Reply by
kasper

2012-10-18
18:09
Hi there,

In recent DC versions, this has been made available if you add the datastore in conf.xml. Like this (with all possible table types enabled - fit to your needs):

<jdbc-datastore name="My datastore">
<url>jdbc:jtds:sqlserver://hostname/database;useUnicode=true;characterEncoding=UTF-8</url>
<driver>net.sourceforge.jtds.jdbc.Driver</driver>
<username>username</username>
<password>password</password>
<table-types>
<table-type>TABLE</table-type>
<table-type>VIEW</table-type>
<table-type>SYSTEM_TABLE</table-type>
<table-type>GLOBAL_TEMPORARY</table-type>
<table-type>LOCAL_TEMPORARY</table-type>
<table-type>ALIAS</table-type>
<table-type>SYNONYM</table-type>
<table-type>OTHER</table-type>
</table-types>
</jdbc-datastore>

Good luck.

Reply by
delostilos

2012-10-18
18:40
Hi Kasper,

Is this a MetaModel feature or a DataCleaner specific feature?

Regards,
JJ.

Reply by
kasper

2012-10-18
18:53
Hi JJ,

The XML is datacleaner-specific, but the table types are defined in MetaModel and passed on to JdbcDataContext in there to filter which tables to query for when discovering metadata about the database.

Reply by
fortuinw

2012-10-25
09:54
Hi Kasper

This is a brilliant addition to the DC.

thanks
Wayne

You need to be logged in to participate

In order to post your own comments on this topic, you need to be logged in.

Username:

Log in by clicking the login link at the top of the screen