You have two options here, either use a TemplateColumn
, or write a render_FOO
method.
Here is an example using the TemplateColumn
(as you can see the record is added to the context that is used to render the template, thus allowing you to access the pk
via record.pk
:
TEMPLATE = '''
<a href="{% url some_url_edit record.pk %}" class="tbl_icon edit">Edit</a>
<a href="{% url some_url_del record.pk %}" class="tbl_icon delete">Delete</a>
'''
class MyTable(tables.Table):
column_name = tables.TemplateColumn(TEMPLATE)
Example using the render_FOO
:
from django.utils.safestring import mark_safe
from django.core.urlresolvers import reverse
class MyTable(tables.Table):
column_name = tables.Column()
def render_column_name(self, record):
edit_url = reverse("some_url_edit", args=[record.pk])
del_url = reverse("some_url_del", args=[record.pk])
return mark_safe('''<a href="%s" class="tbl_icon edit">Edit</a>
<a href="%s" class="tbl_icon delete">Delete</a>'''
% (edit_url, del_url))
As you can see the TemplateColumn
approach is probably a little cleaner in
your case.
TemplateColumn
stuff very obvious, it's only covered in the API Reference at the very bottom. – Wilden