Re: Organization of Java-SQL-DB Interface

2012-04-05 Thread Mattmann, Chris A (388J)
Hi Mike, On Apr 5, 2012, at 1:54 PM, Starch, Michael D (388L) wrote: [...snip..] > > The issue I am trying to solve is that in our operational environment we > are starting to run into trouble because of some subtleties of SQL when > hit with very large databases. Thus we need our DBA to have th

Re: Organization of Java-SQL-DB Interface

2012-04-05 Thread Starch, Michael D (388L)
All, I will agree from a unit testing perspective it makes it more difficult, and it makes it harder to keep the SQL queries safe from manipulation from the outside world after delivery (will be a concern in the future). The issue I am trying to solve is that in our operational environment we are

Re: Organization of Java-SQL-DB Interface

2012-04-05 Thread Mattmann, Chris A (388J)
Hi Mike, On Apr 4, 2012, at 1:00 PM, Starch, Michael D (388L) wrote: > All, > > I am currently working on designing a catalog implementation that interacts > with an oracle database for use with the filemanager component. The current > version uses sql that is inline with the java code. Howe

Re: Organization of Java-SQL-DB Interface

2012-04-04 Thread Mattmann, Chris A (388J)
Hi Brian, I shared your concerns, *and* your enthusiasm. Mike: I think you can use JIRA issue https://issues.apache.org/jira/browse/OODT-393 and we'll be happy to help you shepherd this. Cheers, Chris On Apr 4, 2012, at 1:37 PM, wrote: > hey mike, > > Are you looking do something like th

Re: Organization of Java-SQL-DB Interface

2012-04-04 Thread holenoter
hey mike,Are you looking do something like this?  Storing queries in a file and adding in values utilizing PathUtils replacement:SELECT DISTINCT product_id from MOA_IASI_L1C_Metadata where element_id = 'urn:peate:NominalDate' and element_value = '[NominalDate]';While this is cool and convenient, i

Organization of Java-SQL-DB Interface

2012-04-04 Thread Starch, Michael D (388L)
All, I am currently working on designing a catalog implementation that interacts with an oracle database for use with the filemanager component. The current version uses sql that is inline with the java code. However, a recent need for maintenance to this SQL has highlighted the need to pull