Hello!
In the system we are working on, there is a need to store some
information about an user that is not covered by current Visitor table.
It is not neceserily generic enough, that I would suggest adding it to
the default Turbine database.
We are thinking about correct way of implementing it and these are the
approaches we could think of:
1. Creaing an additional table in the database containg the information
that is not present in Visitor, using VISITORID as a primary key,
and writing SQL statements to access it as necessary
2. Creating an additiona table in the database containg all personal
information about an user, using only VISITORID, LOGINID, PASSWORD_VALUE
and CONFIRMED_VALUE from Visitor (let's say, these are system-level information,
and our table is application-level information).
We could also use Peers model creating classes UserInfomation and
UserInformationPeer, and subclass TurbineMapBuilder as neccessary.
3. Create an SQL script to ALTER TABLE VISITOR ADD ... the fields we want,
Subclass TurbineUser, TurbineUserPeer and TurbineMapBuilder as neccessary.
4. Other possibilites?
Approach 1 is definetely bad, because it's unclear and hard to maintaind,
but we cat't decide between 2 and 3. Any advice is wellcome!
Thanks in advace
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
