2016-04-03 145 views
1

我有一些麻烦,我的第一个Django项目,它必须是一个常见的/容易解决一个!作为一个背景,我正在构建一个用于追踪治疗预约的应用程序。大多数数据结构非常简单,除了需要ManyToMany的一个实例外,还有一个中介(通过)模型。正如你可以在我的models.py中看到的,有三个模型与我遇到的问题有关。联系人模式用于存储客户的联系信息。案例模型是处理一件工作/工作的概念。任何特定的案例都可以有多个会话,依此类推。通常情况下,案例可能有两个或更多联系人将他们之间的账单分开。因此,需要具有中间模型的ManyToMany存储特定联系人将支付的账单的百分比。 models.pyDjango通用视图ManyToMany与“通过”模型

class Contact(models.Model): 
    first_name = models.CharField(max_length=200) 
    last_name = models.CharField(max_length=200) 
class Case(models.Model): 
    invoicees = models.ManyToManyField(Contact, through='Invoicees_Members', through_fields=('case','contact'),null=True, blank=True) 
class Invoicees_Members(models.Model): 
    contact = models.ForeignKey(Contact, on_delete=models.CASCADE) 
    case = models.ForeignKey(Case, on_delete=models.CASCADE) 
    invoice_percentage = models.IntegerField(validators = [MinValueValidator(1), MaxValueValidator(100)],null=True, blank=True) 

我已经做了计算器以及如何处理保存表单提交的其他网站搜索周围的不少。最常见的解决方案似乎是我试图在下面实施的。你会注意到我试图使用通用的基于类的视图(在这种情况下是CreateView)。

views.py

class CaseCreate(CreateView): 
    model = Case 
    success_url = '/cases/' 
    fields = '__all__' 
    def form_valid(self, form): 
     self.instance = form.save(commit=False) 
     for contact in form.cleaned_data['invoicees']: 
      invoicee = Invoicees_Members() 
      invoicee.case = self.instance 
      invoicee.contact = contact 
      invoicee.save() 
     return super(ModelFormMixin, self).form_valid(form) 

不幸的是,表单提交导致以下错误:“异常值:保存()禁止,以防止数据损失,由于未保存的相关对象‘案例’”。我的假设是,出于某种原因form.save(commit = False)不会返回一个ID用于Invoicees_Members模型保存...

有什么想法?这一定是微不足道的,我在这里弄错了。附:我试过用self.object代替self.instance,并遇到同样的错误。

错误&堆栈跟踪:

Traceback: 

File "C:\Python27\lib\site-packages\django\core\handlers\base.py" in get_response 
    149.      response = self.process_exception_by_middleware(e, request) 

File "C:\Python27\lib\site-packages\django\core\handlers\base.py" in get_response 
    147.      response = wrapped_callback(request, *callback_args, **callback_kwargs) 

File "C:\Python27\lib\site-packages\django\views\generic\base.py" in view 
    68.    return self.dispatch(request, *args, **kwargs) 

File "C:\Python27\lib\site-packages\django\views\generic\base.py" in dispatch 
    88.   return handler(request, *args, **kwargs) 

File "C:\Python27\lib\site-packages\django\views\generic\edit.py" in post 
    256.   return super(BaseCreateView, self).post(request, *args, **kwargs) 

File "C:\Python27\lib\site-packages\django\views\generic\edit.py" in post 
    222.    return self.form_valid(form) 

File "C:\Users\danie\Documents\django-projects\office_management\officeman\views.py" in form_valid 
    40.   invoicee.save() 

File "C:\Python27\lib\site-packages\django\db\models\base.py" in save 
    651.       "unsaved related object '%s'." % field.name 

Exception Type: ValueError at /cases/add 
Exception Value: save() prohibited to prevent data loss due to unsaved related object 'case'. 

回答

0

必须保存情况的模型实例保存发票实例之前。这个错误是有道理的,因为Django无法知道案例实例的ID能够将其作为外键保存在发票模型中。 self.instance = form.save(commit=True)。并检查这个链接有关于这个错误的解释在Django documentation

1

由ManyToMany关系引起的保存序列可能存在问题。它能够更好地拥有来自官方文档第一读...

Every time you save a form using commit=False , Django adds a save_m2m() method to your ModelForm subclass. After you’ve manually saved the instance produced by the form, you can invoke save_m2m() to save the many-to-many form data.

例子:

# Create a form instance with POST data. 
>>> f = AuthorForm(request.POST) 

# Create, but don't save the new author instance. 
>>> new_author = f.save(commit=False) 

# Modify the author in some way. 
>>> new_author.some_field = 'some_value' 

# Save the new instance. 
>>> new_author.save() 

# Now, save the many-to-many data for the form. 
>>> f.save_m2m() 

阅读保存方法与实例的完整文档Here