Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
textile and database design: best practices?
Sorry if this is sort of off topic, but I am buidling a CMS for a client, and want to incorperate Textile for body text. I noticed that Textpattern uses two fields to store body information: one raw, one “html”. Anyone on the DEV team (Zem?) care to offer reasons for storing this information seperately (rather then storing one version and then just conditionally applying textile right before page output)?
Jeff.
Offline
Re: textile and database design: best practices?
Though I am not a member of the dev team, I would offer a reason: Performance. It is definitely better to parse the Textile code once per article save than every time a page is requested.
Last edited by wet (2006-04-20 19:41:41)
Offline
#3 2006-04-22 03:57:27
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: textile and database design: best practices?
…I would offer a reason: Performance
ding ding ding, we have a winner.
Offline
Re: textile and database design: best practices?
Definitely makes sense. Thanks.
Offline