Re: Design question: too many SQLs differ by updated columns
Date: Mon, 2 Jun 2008 10:48:07 -0700
On Sat, May 31, 2008 at 4:30 PM, Yong Huang <yong321_at_yahoo.com> wrote:
> We either have
> to redesign the data model, normalizing some columns into their own tables
> (e.e. occupation shouldn't belong in patient table), or query the row first
> list all columns in the update set clause filling in the selected value for
> those columns that don't need to be updated.
Normalizing for performance.
Imagine that. ;)
-- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist -- http://www.freelists.org/webpage/oracle-lReceived on Mon Jun 02 2008 - 12:48:07 CDT