[Home] [By Thread] [By Date] [Recent Entries]

  • From: "Bullard, Claude L (Len)" <clbullar@i...>
  • To: Ronald Bourret <rpbourret@r...>,"Fuchs, Matthew" <matthew.fuchs@c...>
  • Date: Mon, 05 Nov 2001 16:48:39 -0600

And is a chance to clean up.  This is particularly 
useful if retrofitting from a pre-existing database 
such as a relational schema.  

Turns out to be more work than one thinks.  Running 
an auto-normalize utility can be risky.  Given the 
table scoping, things that look like duplicates 
might not be.

len

-----Original Message-----
From: Ronald Bourret [mailto:rpbourret@r...]

"Fuchs, Matthew" wrote:
> 
> I'm not sure what you mean by "dissolve all references and insert it at
the
> referenced place", as to me that seems to be the opposite of
> flattening/normalizing.  I consider normalizing to be hoisting all
> definitions/declarations to the top level and replacing recursive
structures
> with references to the hoisted ones.

I agree. This has the added advantage of not duplicating any
definitions.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member