Re: Design question: too many SQLs differ by updated columns

From: Jared Still <>
Date: Mon, 2 Jun 2008 10:48:07 -0700
Message-ID: <>

On Sat, May 31, 2008 at 4:30 PM, Yong Huang <> 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
> and
> 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

Received on Mon Jun 02 2008 - 12:48:07 CDT

Original text of this message