Docs: From forms.FileField() to ExcelInMemoryUploadedFile ?

[guettli]

I do not understand this:

UploadFileForm is html widget for file upload form in the html page. Then look down at filehandle. It is an instance of either ExcelInMemoryUploadedFile

Source: http://django-excel.readthedocs.io/en/latest/

You use an ordinary forms.FileField(). I guess the matching config in settings.py is needed.

Please make this part more newbee friendly.

What could be added here?

UploadFileForm is html widget for file upload form in the html page. *** here ** Then look down at filehandle. It is an instance of either ExcelInMemoryUploadedFile

[chfw]

OK. I will elaborate more on that in the doc. Thanks for your comments.

In this section, forms.FieldField() tells the UploadFileForm that I will need a form field that accepts a file upload.

And UploadFileForm can be rendered by Django as a html form on your web page and the form instance can also be used to do form validation in the server side.

[guettli]

Don't get me wrong. I just don't know what big benefit django-excel provides.

I use pyexcel like this now:

class FooForm(forms.Form):
    spreadsheet = forms.FileField()

    def save(self):
        temporary_uploaded_file = self.cleaned_data['spreadsheet']
        for row_dict in pyexcel.iget_records(file_stream=temporary_uploaded_file,
                                 file_type=temporary_uploaded_file.name.split('.')[-1]):
            do_foo(row_dict['my_col'])

Why should I use django-excel? Why is it better then the way I do?

I like it reusable. I don't like it, if I need to change the config like settings.FILE_UPLOAD_HANDLERS for one app. I run several apps in my project. What should I do, if app Foo wants Foo-Upload-Handler and app Bar wants Bar-Upload-Handler?

[chfw]

I like your critical thinking. Here is my rationale for django-excel.

django-excel provide two handlers in order to save the time that is to be spent on saving the uploaded file to file system and reading it back for further processing. In particular, MemoryFileUploadHandler would hold the uploaded file in memory. The idea is that ExcelMemoryFileUploadHandler can read excel data from the memory buffer already without saving it to file system first.

Unless you have other means of obtained the uploaded file more efficiently, you can ignore django-excel.

[guettli]

Thank you for your feedback. And thank you for liking my critical thinking.

Above I provided the lines which I use now.

Do you think there is a more efficient way to use pyexcel and django (without django-excel)?

[chfw]

Apart from handling file uploads, you can use pyexcel the way you wanted(I mean without using django-excel). The main challenge for pyexcel is how to read and write data quickly. The performance of pyexcel differs in handling data under 1MB, and hundreds of MB, up to multiple GBs. Here is the list of things that I found in configure pyexcel plugins to cope with big data sets: http://pyexcel.readthedocs.io/en/v0.6.0/iodrivers.html#read-and-write-with-performance.
and here:
http://pyexcel.readthedocs.io/en/v0.6.0/two-liners.html

[chfw]

And when django-excel tries to save the uploaded data into django models, it will use bulk_insert(which is much quicker than saving one by one). However, to be able to use bulk_insert, the developer need to ensure the uploaded data will not cause database exceptions upon db-insersion, typical ones are: database integrity error.

[chfw]

9b79176