Re: Drupal profile table, how to handle this in webobjects?
Re: Drupal profile table, how to handle this in webobjects?
- Subject: Re: Drupal profile table, how to handle this in webobjects?
- From: Jean-Francois Veillette <email@hidden>
- Date: Thu, 12 Feb 2009 10:09:56 -0500
Le 09-02-12 à 05:40, Johan Henselmans a écrit :
As you might notice, for a profile of a person with, let's say, 20
attributes, one would end up with a smorgasbord of 20 records in
default_profile_values.
I have two questions:
-would it be possible to replicate such a thing in WebObjects? I can
imagine creating the default_profile_fields table, that should not
be too hard. Creating the form using the data from the
default_profile_fields, and the values from default_profile_values
fills me with ?wonder?.
Yes, certainly possible !
-will it blend, sorry, will it scale? I have doubts about this
schema when you start having large amounts of users. The enormous
amount of records that have to be fetched for for the profile of a
user make me question if this will be scalable.
I would not be afraid of scalling such system, most of the data is
read only (the structure of the permissions when / where they are
used) so it can be put in the shared editing context, or defined as
read-only and cache in memory.
It only leave you with the data per user and per profile, which is
only fetched once per user ... no big deal.
Any ideas about this?
I have used a similar system that I build few years ago, it work very
well !
Examples of other WebObjects projects that do something similar?
Here is a similar setup that was build for a school. The idea was to
let individual users have personalized attributes without being forced
to define it for all users by using profiles.
We have a hierarchical profile structure ... see (this is an old
project that never got the care of a careful interface designer) :
From this screenshot, you can see the edit mode for « Enseignant ».
For each attribute, you can see the value assigned. If the value is
static (a string) it mean that it is inherited, you can click « + » to
have it custom to this profile. If the value is custom, you can click
« - » to remove it and have the value inherited.
This screenshot if from a system with only 9 properties that need to
be evaluated. In this system, we have about 300 users, but often only
5 logged-in max at the same time. This system is running great.
We have a similar edit attribut screen for user, either the attribute
is custom (overide the profile) or is inherited (use the value from
the profile).
I have a similar setup in another system where we have roughly 200
properties as part of the profile, the profile are flat (no
hierarchy), but again, no problem there as well.
I might be able to share some of the code, if you need, just ask, I'll
see what I can do.
- jfv
_______________________________________________
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