Hi,
On May 22, 8:54 am, djangoista <[EMAIL PROTECTED]> wrote:
> Thanks a lot for your reply - I think I'll do that, thats a good point
> about space being cheaper, especially as its just plain text.
Just for the record, the Django site has a nice cookbook article that
discusses this.
http://co
Thanks a lot for your reply - I think I'll do that, thats a good point
about space being cheaper, especially as its just plain text.
On May 22, 1:48 pm, Eric Abrahamsen <[EMAIL PROTECTED]> wrote:
> I don't know what the standard is, but I'm doing exactly what you
> detail here: two DB fields, o
I don't know what the standard is, but I'm doing exactly what you
detail here: two DB fields, one that stores Markdown text, and
another, not visible in the Admin interface, that stores HTML. In the
save method, one gets dumped into the other, via the markdown filter.
If you or one of your
Hi,
I'm about to start on a simple django-based blogging engine (I'm sure
there are already many out there, but I want to have a go a creating
one from scratch). I'm planning on using Markdown (lightweight markup
language) for creating blog posts, but I'm not sure what to store in
the DB.
One opt
4 matches
Mail list logo
