Hi Patrick,
 
I've commited an enhancement for Abator to SVN for this issue.  You can check the source out from SVN and build it to test in your environment.
 
Following the example we've been discussing, this configuration generates objects properly for the public synonym "FRED" that points to "HR.EMPLOYEES":
 
<table schema="HR" tableName="EMPLOYEES">
  <property name="ignoreQualifiersAtRuntime" value="true" />
  <property name="runtimeTableName" value="FRED" />
</table>
 
There's also a new page in the Abator documentation for Oracle that describes this enhancement.  Let me know how this works for you.
 
Jeff Butler


On 9/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:
I'm using plain abator.
-----Original Message-----
From: Jeff Butler [mailto: [EMAIL PROTECTED]]
Sent: Thursday, September 28, 2006 3:55 PM
To: dev@ibatis.apache.org
Subject: Re: Abator introspection patch

Sure - I understand you'll have to restrict Abator to a specific schema - but my enhancement would allow you to tell Abator not to include the schema in its generated SQL.
 
I think the way to deal with synonyms would be to generate against the table the synonym pointed to - but make abator write the code to interact with the synonym rather than the specific table.  This would also be possible with my proposed enhancement.  So if you have synonym FRED pointing to HR.EMPLOYEES, you could generate against HR.EMPLOYEES, but have abator write the SQL to FRED.
 
Are you using the eclipse plugin or plain abator?  If you're using plain abator, then I'll get something committed in a day or two and you could try it.
 
Jeff Butler

 

Reply via email to