Best Practice: Modify c5 db or use separate db for user-generated data?
Permalink
I am building a site where users will be generating much of the content. Does it make sense to modify the c5 database (adding tables and modifying others), or is it better to keep these things separate?
It would be simpler to keep everything in one database, but I'm not sure if I want to risk corrupting something critical to the site with a user operation.
It would be simpler to keep everything in one database, but I'm not sure if I want to risk corrupting something critical to the site with a user operation.
It all depends on how users are going to modify data. If it is with SQL, then @Brainakazariua's recommendation is the way to do it.
If it is with prepared, tested and properly escaped queries built into c5 blocks or single pages where the user enters data into a form field and it is all fully validated before the php then inserts the data, there is no reason for it to be separate.
Either way, make sure you take regular backups so you can revert to valid data if something screws up.
If it is with prepared, tested and properly escaped queries built into c5 blocks or single pages where the user enters data into a form field and it is all fully validated before the php then inserts the data, there is no reason for it to be separate.
Either way, make sure you take regular backups so you can revert to valid data if something screws up.
if you have everything in a single database then everything goes down when they mess up, on the other hand if the Concrete5 data is in a different database then they have no way of breaking that