I'm going to implement a light formatting language (probably cloth, possibly markdown) on which I'm working , And I wonder how best to store it in the database.
If users are posting content, then I understand that the original, non-converting markup is stored so that the user does not have to edit the HTML the next time. But since the material is being fully displayed from the edit, it still makes sense to store a copied copy of the content, so that each page is basically sent through the textile Could.
So, is the general practice to store both the original and converted content in the database? Is there a better way?
Thank you! Store Markdown:
- Every View = Conversion
Store HTML
- Not every visual = processing
- every edit = markerdown and on the back
Store both
- Edit each view = any processing
- edit
You have to make your processing costs versus your storage costs.
Comments
Post a Comment