Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

Actually that was the point in creating a new thread about possible bridges between OO mechanisms for helping better relational implementations through JAVA. The premise here is to assume that some OO distinctive features may reinforce some relational requirements. The point here of course is NOT about overthrowing SQL as this language is still the most comprehensive to date for data manipulation and definition but rather to establish a cooperative discussion between people knowledgeable about data management and OO people. All people interested...

Here is the link...You may check it out...

http://groups.google.com/group/comp.databases.theory/browse_thread/thread/54e82593b205a2a8

Andrew McDonagh wrote:
> phlip wrote:
> > Andrew McDonagh wrote:
> >
> >> Well for PL/SQL there is ut/PLSQL (http://utplsql.sourceforge.net/)
> >
> > DBs are easy to unit test because they have clean, responsive, and
> > abstracted interfaces.
> >
> > DBs are hard to refactor, and grow their designs in response to real-world
> > issues. I suspect that's the purpose of the book /Refactoring Databases/
> > by Ambler Sadalage is about.
> >
>
> Agreed.
>
> As for refactoring, most of the difficulty comes down to the limitations
> of the store procedure language and development environments not
> supporting automated refactorings.
>
> Its possible, just difficult and manual.
>
> One point no one has yet addressed is the use of Java within rdbms - it
> would be interesting to see what issues we have with that.
>
> From personal exposure, it allows for far greater control, development,
> unit testing, refactoring than the store procedure language like PL/SQL.
Received on Fri Jun 02 2006 - 21:32:45 CEST