So, I'm curious as I'm setting up tables and settings for a new site what your opinions and the pros and cons of using extended user profiles vs. storing the information in a separate table.
For instance MODx is going to store basic login information such as username and password and has the capabilities of storing some built in fields as well as extended fields. At the same time those extended fields could be stored in a separate table.
Does anyone have an opinion on the method of storing additional user details? Are there benefits to doing it one way over another?
-
☆ A M B ☆
- 24,524 Posts
Other than being a little easier to set up, there are no advantages I can think of to using the extended field in the user profile. The only time I would ever use that field is if I were creating the data in code and was positive that I'd never need to search or sort by it.
Bob,
I've looked over the Class Extender documentation on your website. I'm curious when modifying the schema there is the basic modx user table reference and the extended user table. Could the entire database schema be established though this add-on? Meaning all tables that could have a foreign key related to the Modx user id?
I could see several many-to-one relationships related to the modx user id as opposed to just extending the user data.
TBH, I'm not sure -- I've never done more with it that extend modUser and modResource. It might well work, but I couldn't guarantee it. If you try it, let me know.
