handle MultipleObjectsReturned for form data

[chhantyal]

We also need to handle MultipleObjectsReturned as we allow nullable display_key in table. So when display_key url param is empty, above exception is raised.

We could also do,

if display_key:
        data = FormModelData.objects.get(display_key=display_key)
else:
        data = None

Let me know which one you prefer.

[MarkusH]

I'd prefer the if approach:

data = None
display_key = ...
if display_key is not None:
    data = ...

[MarkusH]

Could you also add a test case to tests.test_views to check for the behavior, please.

[chhantyal]

Sure, will add tests later in the evening

[MarkusH]

Thanks. If you rebase to the current develop branch the tests for Django 1.8 should pass. I just pushed a fix.

[coveralls]

Coverage remained the same when pulling e0ba2d5 on chhantyal:develop into 2e7d3fc on MarkusH:develop.

[coveralls]

Coverage decreased (-0.1%) when pulling afdbef9 on chhantyal:develop into 2e7d3fc on MarkusH:develop.

[chhantyal]

Sorry wrong branch, I forgot Github updates PR. But this commit might be good thing to pull in upstream https://github.com/chhantyal/django-dynamic-forms/commit/3ffc28c16211b33f4e69c5125d6e2066991896f5

[coveralls]

Coverage decreased (-0.1%) when pulling afdbef9 on chhantyal:develop into 2e7d3fc on MarkusH:develop.

[coveralls]

Coverage decreased (-0.1%) when pulling b2d9775 on chhantyal:develop into 2e7d3fc on MarkusH:develop.

[coveralls]

Coverage decreased (-0.1%) when pulling b2d9775 on chhantyal:develop into 2e7d3fc on MarkusH:develop.

[MarkusH]

Can you please submit 3 independent pull requests for the features.

• Custom receivers per form (Allow different email receivers per form #13)
• Rename the label in admin (Rename label in Admin to "Dynamic Forms" #14)
• The topic of this PR (MultipleObjectsReturned error thrown if display_key is empty in success view #15)