Welcome to the dBforums forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

If you prefer not to see double-underlined words and corresponding ads, place your cursor
here for ContentLink opt out.

Go Back  dBforums > General > Database Concepts & Design > using nested tables

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-08-03, 20:01
pcdunham pcdunham is offline
Registered User
 
Join Date: Jul 2003
Posts: 11
using nested tables

Could someone give an example of when a nested table, or varray would be applicable? I have restrained from using them mainly because I don't think there is any way to use them with cmp entity beans. Is there a way to use them with cmp entity beans? The only situation I can think of is if there was say a user with a corresponding table that contained a nested table for something like user propeties. It seems that collection types are more for speed and organization than normalization.
Thanks,
Philip
Reply With Quote
  #2 (permalink)  
Old 07-09-03, 07:10
andrewst andrewst is offline
Moderator.
 
Join Date: Sep 2002
Location: UK
Posts: 4,874
Re: using nested tables

Quote:
Originally posted by pcdunham
Could someone give an example of when a nested table, or varray would be applicable? I have restrained from using them mainly because I don't think there is any way to use them with cmp entity beans. Is there a way to use them with cmp entity beans? The only situation I can think of is if there was say a user with a corresponding table that contained a nested table for something like user propeties. It seems that collection types are more for speed and organization than normalization.
Thanks,
Philip

They are a violation of 1st normal form but appeal to OO programmers who don't appreciate the value of normalisation.
__________________
Tony Andrews
http://tonyandrews.blogspot.com
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On