Autumn

This is an appengine datastore problem, unfortunately. Grumble grumble.

I actually can't recommend doing this FK column just yet. The type information on the other side of the FK needs to be known in advance of the filter step...

I would like to change this in the near future, since this is an issue I think comes up for people expecting to use it like models or forms. The...

Oops, didn't mean to close :P

Yeah, making the view forward a 'user' kwarg via ``get_datatable_kwargs()`` is the correct way to do it (pretty much like vanilla forms). The design idea was that the base queryset...

There are a couple of options, but right now none are as direct as a kwarg to the Column constructor. I need to allow `attributes` so that you have some...

> > since all of the built-in columns we provide wouldn't benefit from it. > > Why not? being able to set column width might be needed once in a...

Yeah, default Model.Meta ordering can mess up a datatable if the named model field isn't actually on the datatable, which is a problem with how the datatable cleans the ordering...

No promises on timeline yet, but this is on my todo list for a new release

We'll have to look at that for 1.1 and tie it to the view with a form class. We do use a form class internally, but it's a pretty dynamic...