Hessam Posted September 12, 2018 Share Posted September 12, 2018 According to this link , it says that it's recommended to create new tables for new module. Is it true about the existing entities? (like customer, cart, product etc.) I think we should not create new tables for somethings like these cases, and we should modify the existing tables (e.g to add a field to customer table). Is it true? And when we modify the existing tables, should we override the classes? (e.g we want to add a field to customer, should we modify the corresponding class for customer- for active records) Link to comment Share on other sites More sharing options...
Rolige Posted September 12, 2018 Share Posted September 12, 2018 By altering the native database tables probably you will kill the future updates of PrestaShop, that’s why you need create your own ones and handle it from a module or override file. Link to comment Share on other sites More sharing options...
Hessam Posted September 16, 2018 Author Share Posted September 16, 2018 On 9/12/2018 at 6:02 PM, Rolige said: By altering the native database tables probably you will kill the future updates of PrestaShop, that’s why you need create your own ones and handle it from a module or override file. Thanks for your reply. But creating my own tables means creating my own active record classes? What if the native table has so many relationships with other tables? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now