Feature request: use verbose_name instead of field name for column names
See original GitHub issueWhen your exporting data from your database as xls or csv it’s usually for human reading so it would be nice if the column names would be the verbose_name of the model fields. i.e. “Company name” instead of company_name for a field: company_name = models.CharField(_('Company name'))
As far as i can tell this is not currently possible, even just passing a display_name value to a (custom) field for a resource would be a nice fix…
Issue Analytics
- State:
- Created 10 years ago
- Comments:14 (2 by maintainers)
Top Results From Across the Web
How to write not field name but verbose name of field in this ...
I may be misinterpreting the question, but if you want to change field.name: for field in opts.fields: field.name = 'Foo'.
Read more >Reserved Field Names - Amazon Forecast
Amazon Forecast reserves the following names. You can't use these names for your schema fields or dataset headers. A. A. ABORT.
Read more >verbose_name - Django Built-in Field Validation
A human-readable name for the field. If the verbose name isn't given, Django will automatically create it using the field's attribute name, ...
Read more >Documentation: 15: psql - PostgreSQL
Specifies the name of the database to connect to. This is equivalent to specifying ... Turn off printing of column names and result...
Read more >Database Engine events and errors - SQL Server
Too many table names in the query. The maximum allowable is %d. 107, 15, No, The column prefix '%.*ls' does not match with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@gnuhpc here is an updated solution working with Django>=1.9:
If your resource class have custom field, code can be as follows: