You could create another one table called user_details where store the user_id and additional fields you need.
I did something like this. It works great. – brennanag Sep 16 '10 at 16:45 enjoy!
:) I made a multilingual project in such a way. – franzose Sep 18 '10 at 2:16.
Just add the details to the user table and extend the Model_Auth_User class.
I like this idea, but I don't understand enough about the underpinnings of how Kohana works to want to change the Auth system's model. – brennanag Sep 16 '10 at 16:45.
It will allow users to log in with an email and password. There will be other information collected from the user that is pertinent to the sites functions. Using the supplied Kohana Auth module, should I store the separate data in another table?
Id, username, email, password, logins, last_login. Should I create another table or just extend this table? How would you do this?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.