morlandi

That would be a "1 to many" relation, I guess .. there is a limited support for this, please try (from the example project): ``` column_defs = [ ..., {'name':...

I don't understant this in `customize_row()`: ``` mod = obj.tag_set.get(tag1=obj) ``` Maybe you need somethig like: ``` def customize_row(self, row, obj): tags = obj.tag1_set.all() row['Tag_set'] = ', '.join([t. some_name for...

Oh, thank you ... that's really puzzling, isn't it? I will label this issue as a bug and sooner or later hopefully investigate it. In the meantime, a quick and...

I would add an appropriate default ordering to the Model to make sure that when issuing a second query to populate the second page, the underlying queryset is extracted in...

I recently had a similar problem in a completely different context, and I do believe it is an SQL-related issue. When paginating, you should always provide a list of fields...

Thank you @GGosseyn .. I think you can safely go ahead with POST. I will include it in the library sooner or later, but would like to make some extensive...

Hello @MichaelDacanay, thanks for the interesting question. When using DataTables.net in Ajax mode, two views are needed: the first "traditional" for rendering the HTML table, and the second "solicited via...

I would rather override `change_list.html` The template doesn't need to know where the AjaxDatatableView-derived view lives; just provide a url to the latter, and refer to the url in the...

Any progress on this issue ? Do you think it's feasible ? Should you have some documentation or reference about the possible strategies to share, I might contribute, as I'll...

What a good news ! It sound very feasible indeed Thank you @remicaumette