• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
RE: An interesting database question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: An interesting database question


  • Subject: RE: An interesting database question
  • From: "Jonathan Fleming" <email@hidden>
  • Date: Thu, 08 Apr 2004 01:35:33 +0100

Check this out: http://www.cctc.demon.co.uk/normalise.htm

Jonathan F ;^)


From: John Spicer <email@hidden>
To: WOdev List <email@hidden>
Subject: An interesting database question
Date: Wed, 7 Apr 2004 17:16:42 -0500

We will have a database (accessed with webobjects, of course!) that will have accounts in it that information is written into.

We will also have N patients (N being an unknown number).

All the databases I've seen would do this as one table (account) with some way of identifying which row belongs to which patient.

That's probable because it's the most effecient and normalise way to do this.


It has been proposed that instead of one accounting table, we have N tables, one for each patient.

I can't really see why you would want to go down this road.... for what benefit?


Each table would be created on the fly (from the app) using some kind of eo modeler commands.

Why don't you just create an account for that patient on the fly ( a database row ), within a patient table, that's do just what you want and stay within the confines of dabase normalisation.


I don't know if it's possible yet. I don't know if the database we deploy would allow creation on the fly (due to licensing considerations, perhaps).

If you are using a RDMS (Relational Database Management System), regardless of licensing consideration, it'll be able to do this for you due to your coding of course.


The question I guess is in three parts:

[1] Can it be done using EOModeler calls on the fly;

Yes, but not even worth entertaining. Bad move.

[2] Has anyone seen it done, and if so, why?

No.

[3] Should it be done?

No.

Thanks in advance for any advice on this.

You're welcome

_________________________________________________________________
Tired of 56k? Get a FREE BT Broadband connection http://www.msn.co.uk/specials/btbroadband
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.



  • Prev by Date: Re: An interesting database question
  • Next by Date: UTF-8 in generated e-mails?
  • Previous by thread: Re: An interesting database question
  • Next by thread: java.io.IOException: No serializer found for class...
  • Index(es):
    • Date
    • Thread