Re: [Dunit-interest] Is Dynamic SQL worth refactoring?

[Mark W. <mw...@st...>]

From: "Michael A. Johnson" <csm...@ho...>

> Couldn't this be hidden in the implementation of the object? Or at least
> a descendent of the sql writer ie
>
> SQLInsert_BDE, SQLInsert_Oracle, SQLInsert_ADO?

Of course.   The SQL writer is where it should be.  My point was about the
implementation of the SQL writer.  Many programs often take the approach of
hard coding the SQL statements with the values embedded in them.  Then, at
least with Oracle, they then have to deal with customers complaining about
poor performance and customer DBA complaining about their abuse of Oracle.
Believe me, at my last position we had several commercial applications that
did this (hard code SQL) and the performance hit was considerable.

The concept of having an abstract  SQL , or a SQL writer interface with
implementations specific to the platform is the right way to go.
-Mark