[eluser]Peng Kong[/eluser]
[quote author="lsemel" date="1270901441"]Question: My site is going to have a lot of stuff in the account details, and I think I am going to store them in something more flexible like MongoDB so I don't have to create loads of columns full of serialized data storing people's profile fields.
So, if I swap out the account details model with something else, edit the account settings and account profile views and their corresponding controllers, is that going to break anything? Or what other changes would I have to make?
Having the account details be flexible and modular, separate from the rest of the module, would be a good idea because it'll vary based on different use cases, and when you update the module you don't want to destroy your changes.[/quote]
Nope that should NOT break anything! erm... i have no experience in mongodb (tho i would love to go into that very soon)... but changing db should break a3m. That's the whole point why i kept the models so light weight... as long as their doing what their suppose to do everything should work. discuss with me how you're going to integrate mongodb maybe... then i'll be able to give you an idea what to look out for.
yep exactly account details model is meant to be customized according to specific needs.
that why i separated it out into a table, model, and two views... one for public details and one for private details. hack to your own needs was my idea... or should i have architectures it in some other way?
How should i have done it so that when people upgrade a3m their changes are not destroyed? cuz a3m itself is so... it's not a framework... it's a implementation. but ok let me think about it. give me any suggestions pls.
