• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Joining Strategies

 
Ranch Hand
Posts: 393
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Consider the following entity class hierarchy:

public abstract class Account{ }
public class CheckingAccount extends Account{ }
public class SavingsAccount extends Account{ }

Assuming that JOINED is used as Inheritance strategy, and all the three classes are Entity classes, which of the following is correct?

1. Two tables, one for SavingsAccount and one for CheckingAcount will be used.
2. JOINED is an invalid strategy for this scenerio.
3. Three tables, one for each class, will be used.
4. Only one table will be used.

Should the correct answer be 1 nstead of 3. Enthuware says 3 is correct?
 
This will take every ounce of my mental strength! All for a tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic