Re: An interesting database question
Re: An interesting database question
- Subject: Re: An interesting database question
- From: Ray Ackland <email@hidden>
- Date: Thu, 8 Apr 2004 10:54:35 +1200
John,
I don't know if it is possible, but I would say it would be
discouraged. It kind of goes against design concepts, and I imagine it
would slow things down *greatly* - not to mention I can't personally
see the benefits of doing it this way.
But then, most great inventions were done by not following the rules!
r.
On 8/04/2004, at 10:16, John Spicer wrote:
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.
It has been proposed that instead of one accounting table, we have N
tables, one for each patient.
Each table would be created on the fly (from the app) using some kind
of eo modeler commands.
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).
The question I guess is in three parts:
[1] Can it be done using EOModeler calls on the fly;
[2] Has anyone seen it done, and if so, why?
[3] Should it be done?
Thanks in advance for any advice on this.
_______________________________________________
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.