What is the standard way of handling additional data associated with users? For example, in my app each user is associated with one or more supervisors who can authorize them (or not) to execute certain actions. My guess is, since this data is relevant to my app only, it should be placed in a separate set of tables under control of my app, right? Is there any other, better, way of achieving this? I would hate to have to touch Turbine's shipped table schemas... Thanks in advance, -- Gonzalo A. Diethelm [EMAIL PROTECTED] ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
