sknutsonsf
sknutsonsf
Thanks for clarifying. Django 1.8 does not have the JSON field type. I'll be trying out the jsonfield module which claims to be 1.8 compatible. I also have to solve...
Please add the answer from #138 (linked above) to the FAQ or as part of the package description.
Could you please add a migration guide from V6? We have a dozen components that will need to be migrated
> I don't think we'll write a migration guide, too many things have been rewritten or changed. I'm disappointed. It would be very helpful to have a list of "top...
The bug appears to be related to Python 3.9 in some way. It still occurs with the older versions but in the python 3.9 environment. The requirement is for a...
I'm having a similar issue, but in my test case the number of markers and polylines remains constant after the 4'th re-render (there are separate server calls to get the...
There is need for some open source license. MIT or Apache 2 are the best license to encourage commercial use and forks. Please do not make your own license
Workaround (hack really) is to edit the migrations after they are created and before running, to add managed=False. ``` options={ 'ordering': ('-history_date', '-history_id'), 'db_table': 'equipment_historicalequipment', 'verbose_name': 'historical sensor item', 'get_latest_by':...
I was not able to work around the need to edit the generated migration. I looked briefly into the code and it would take at least 4 or 5 hours...