Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

1.0.9 broke uselist=False on backref

See original GitHub issue

In 1.0.8, I could have relationships with uselist=False with no problem (it’d just look strange with how you could actually add multiple entries in the UI…), but in 1.0.9, this instead displays the same symptoms described in #376. And just like in #376, the fix is to move the uselist=False from the backref to the relationship.

Issue Analytics

State:
Created 9 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

3reactions

mrjoescommented, Mar 16, 2016

Goal is to edit two related models at once? Also, is there a chance that another model might not exist (your foreign keys are nullable)?

In any case, I’d use wtforms machinery to do it: http://wtforms.readthedocs.org/en/latest/fields.html#wtforms.fields.FormField

Only problem with this approach - you will have to override populate_obj in your form and create instance of related model if related model does not exists.

0reactions

bepetersncommented, Sep 21, 2016

@nshelly, Any update on how/if you got this to work? I’m looking at using 1-to-1 inline model as well, possibly.