Re: Design Ideas
Re: Design Ideas
- Subject: Re: Design Ideas
- From: Calven Eggert <email@hidden>
- Date: Thu, 23 Jun 2016 09:11:11 -0400
Our app will not have the ability to create tables, columns, etc. in the production environment. Tables will have to be already created.
Calven
> On Jun 23, 2016, at 9:05 AM, Stavros Panidis <email@hidden> wrote:
>
> Hi Calven,
>
> Definitely I am not an expert! I am a amateur (translation to Greek language is erasi texnis which means the lover of art).
>
> I faced the same question some years before, for the same exactly target. I found a solution and it works for around 3 years now at the department of Nephrology, Papageorgiou General Hospital, Thessaloniki, Greece.
>
> It is something like FileMaker where the user can create his own tables, adding desired variables to each table, even after a table has been created and filled with data
>
> As a general design outline I use EO to make my own schema backbone and then I use raw sql to communicate with database.
>
> Hope I helped little.
>
> Best regards
>
> Stavros
>>
>> Message: 4
>> Date: Wed, 22 Jun 2016 11:33:30 -0400
>> From: Calven Eggert <email@hidden>
>> To: WebObjects-Dev <email@hidden>
>> Subject: Design Ideas?
>> Message-ID: <email@hidden>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi all,
>>
>> My question is not simply a WO question, however, perhaps the WO experts have a best practice way of doing this in WOnder.
>>
>> I've been asked to design an application that tracks a process that a patient goes through, with the following:
>>
>> 1. Each patient will follow one of many different paths.
>> 2. Each path consists of a number of activities and the order of the activities along that path.
>> 3. At the moment there are 3 different paths and 15 different kinds of activities. Each activity has different fields to store in the database. (Approx. 5 fields per activity X 15 activities = 75 fields)
>>
>> It would be great if the application could be designed so that new paths/activities can be created by the user in an administration section, as opposed to having the developer create new versions of the application each time a new path/activity needs to be created. Right now, I'm prepared to soldier through and simply design it so that there is 1 table for each activity. I've looked at creating a generic table that has many string fields and then storing the field type, etc, however, this seems like way too much work (validation, etc.). Also thought about one activity table but 75 fields sounds unmanageable plus the fact that there will be more activities added in the next year.
>>
>> Anyone else out there have a different solution or idea?
>>
>> Calven
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lists.apple.com/archives/webobjects-dev/attachments/20160622/d1c792a3/attachment.html>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Webobjects-dev mailing list
>> email@hidden
>> https://lists.apple.com/mailman/listinfo/webobjects-dev
>>
>> End of Webobjects-dev Digest, Vol 13, Issue 264
>> ***********************************************
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
| References: | |
| | >Design Ideas (From: Stavros Panidis <email@hidden>) |