Re: Abator introspection patch

2006-09-29 Thread Jeff Butler
abator. -Original Message-From: Jeff Butler [mailto: [EMAIL PROTECTED]]Sent: Thursday, September 28, 2006 3:55 PMTo: dev@ibatis.apache.orgSubject: Re: Abator introspection patch Sure - I understand you'll have to restrict Abator to a specific schema - but my enhancement would allow

RE: Abator introspection patch

2006-09-28 Thread Patrick.Higgins
I'm using plain abator. -Original Message-From: Jeff Butler [mailto:[EMAIL PROTECTED]Sent: Thursday, September 28, 2006 3:55 PMTo: dev@ibatis.apache.orgSubject: Re: Abator introspection patch Sure - I understand you'll have to restrict Abator to a specific schem

Re: Abator introspection patch

2006-09-28 Thread Jeff Butler
s and apply the unqualified schema resolution rules. Ugh. -Original Message-From: Jeff Butler [mailto: [EMAIL PROTECTED]]Sent: Thursday, September 28, 2006 3:32 PMTo: dev@ibatis.apache.orgSubject: Re: Abator introspection patch Not so...FRED is a public synonym (not in any schema).  It's just O

RE: Abator introspection patch

2006-09-28 Thread Patrick.Higgins
d. We might need to code a special Oracle introspector to look at the system views and apply the unqualified schema resolution rules. Ugh. -Original Message-From: Jeff Butler [mailto:[EMAIL PROTECTED]Sent: Thursday, September 28, 2006 3:32 PMTo: dev@ibatis.apache.orgSubject: Re:

Re: Abator introspection patch

2006-09-28 Thread Jeff Butler
Not so...FRED is a public synonym (not in any schema).  It's just Oracle JDBC wierdness with synonyms.  I saw all kinds of wierd things in my testing.   Maybe you misunderstood my proposed fix...I'm proposing a way for you to GENERATE against a specific schema, but RUN without any schema specified.

RE: Abator introspection patch

2006-09-28 Thread Patrick.Higgins
olver throws an exception rather than returning null for entities it doesn't recognize, so you can't define your own entities in the DOCTYPE. -Original Message-From: Jeff Butler [mailto:[EMAIL PROTECTED]Sent: Thursday, September 28, 2006 11:02 AMTo: dev@ibatis.apac

Re: Abator introspection patch

2006-09-28 Thread Jeff Butler
Never mind - I installed Oracle myself and did some testing.  Here's what I found...   getColumns() won't return data from synonyms unless the "includeSynonyms" property is set to true on the DB connection.  Even then, getColumns() will return the schema of the target table.  For example, I created

RE: Abator introspection patch

2006-09-28 Thread Patrick.Higgins
orgSubject: Re: Abator introspection patch Following your example...   I'm assuming DatabaseMetaData.getColumns(null, null, 'BAR', null) would return columns for both the public alias BAR and PAT.BAR.   However, could you try DatabaseMetaData.getColumns(null, '

Re: Abator introspection patch

2006-09-27 Thread Jeff Butler
not sure if the ResultSetMetaData would have any data or not. -Original Message-From: Jeff Butler [mailto: [EMAIL PROTECTED]]Sent: Wednesday, September 27, 2006 2:30 PMTo: dev@ibatis.apache.org Subject: Re: Abator introspection patch Some questions...   How does the actual table get

RE: Abator introspection patch

2006-09-27 Thread Patrick.Higgins
imagine that's a very expensive operation on some DBs. It's probably expensive on Oracle, too. I thought about trying "select * from tablewhere where 1 = 2", but I'm not sure if the ResultSetMetaData would have any data or not. -----Original Message-From: Jeff Butle

Re: Abator introspection patch

2006-09-27 Thread Jeff Butler
Some questions...   How does the actual table get selected at run time?  Is there a default schema specified on the db connection?  Or, are the aliases not in a schema and there is some way to switch the aliases to the proper schema at runtime?   Do you actually want to generate the artifacts base