Re: An interesting database question
Re: An interesting database question
- Subject: Re: An interesting database question
- From: Dov Rosenberg <email@hidden>
- Date: Wed, 07 Apr 2004 20:35:01 -0400
The bigger problem is how do you scale your design to include 10000
patients? Having 10000 individual tables is not practical from both a
database storage perspective or a performance one. Databases are optimized
to cache data by table.
Dov Rosenberg
Conviveon Corporation
http://www.conviveon.com
On 4/7/04 6:46 PM, "Jonathan Rochkind" <email@hidden> wrote:
>> [1] Can it be done using EOModeler calls on the fly;
>
> Maybe. But it's going to be a big pain. [PS: It's not "EOModeler"
> calls you are talking about; EOModeler is a developer tool. You're
> talking about the Enterprise Objects Framework, EOF.]
>
>> [2] Has anyone seen it done, and if so, why?
>
> No.
>
>> [3] Should it be done?
>
> I don't think so. That's not really the way that relational
> databases are meant to be set up. Even if you weren't using WO/EOF, I
> wouldn't think it would be a good idea, and can't see why you'd want
> to do it. With WO/EOF----it becomes even a worse idea, because EOF
> is not expecting things to be set up like this. I think you're going
> to have a lot of trouble getting it to work----for a purpose you have
> not identified (and seem to be asking others to suggest!). What was
> the purpose that whoever proposed this scheme had in mind?
>
> --Jonathan
>
>
>> Thanks in advance for any advice on this.
>
>
> At 5:16 PM -0500 4/7/04, 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:
>> _______________________________________________
>> 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.
> _______________________________________________
> 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.
_______________________________________________
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.