John McNally wrote:
> Assuming this is not done while the application is live, it should be
> possible to add a column to the database to accept data from an "attribute
> (the Perm hashtable)". The admin adds the column which has the name of the
> key. The app is started and TurbineUserPeer is then aware of the column.
> It is a problem as it is currently written that the new empty column would
> overwrite the value stored in OBJECTDATA the last time the user was saved.
> I think this should be changed, so that when including the attributes stored
> in named columns if a key is already present in Perm, (and maybe that the
> column data is null or "", etc.) the data in Perm stays, so that the next
> time the user is saved the column will get populated. Anyone see a problem
> with this?
Generally, the decisons which attributes should be kept in separate
columns should be made before the applications starts populating
the database. But what you wrote makes perfect sense. We should read from
named columns, and then from OBJECTDATA. (and document why it's done
this way :))
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
