Databases
StackOverflow2013
Postsdbo
PODjango parameters read in wrong order
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango parameters read in wrong order
    primarykey
    data
    text
    <p>I have the following model:</p> <pre><code>class Work(models.Model): title = models.CharField(max_length=30) amount = models.PositiveIntegerField() percent = models.FloatField(validators=[MaxValueValidator (100),MinValueValidator(0)]) drop = models.PositiveIntegerField(default=0) assignments = models.ManyToManyField(Assignment) </code></pre> <p>but when I create some "work", it acts oddly:</p> <pre><code>In [6]: homework = Work("homework",12,15) In [7]: homework.save() --------------------------------------------------------------------------- ValueError Traceback (most recent call last) ... #lots and lots of stuff...I will post the extend at the bottom ... ValueError: invalid literal for int() with base 10: 'homework' </code></pre> <p><strong>Why is it reading that the first parameter should be an int when the first parameter requires a CharField?</strong></p> <p>I think what I said makes sense. <code>homework.title</code> should be "homework", <code>homework.amount</code> should be 12, <code>homework.percent</code> should be 15, and <code>homework.drop</code> should be the default: 0.</p> <p>Can somebody explain why it comes up with this error and how I can fix it. Thanks in advance.</p> <h1>full error result:</h1> <pre><code>In [6]: homework = Work("homework",12,15) In [7]: homework.save() --------------------------------------------------------------------------- ValueError Traceback (most recent call last) /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/core/management/commands/shell.pyc in &lt;module&gt;() ----&gt; 1 homework.save() /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/base.pyc in save(self, force_insert, force_update, using, update_fields) 544 545 self.save_base(using=using, force_insert=force_insert, --&gt; 546 force_update=force_update, update_fields=update_fields) 547 save.alters_data = True 548 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/base.pyc in save_base(self, raw, cls, origin, force_insert, force_update, using, update_fields) 620 # no force_insert) 621 if ((force_update or update_fields) or (not force_insert and --&gt; 622 manager.using(using).filter(pk=pk_val).exists())): 623 if force_update or non_pks: 624 values = [(f, None, (raw and getattr(self, f.attname) or f.pre_save(self, False))) for f in non_pks] /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/query.pyc in filter(self, *args, **kwargs) 665 set. 666 """ --&gt; 667 return self._filter_or_exclude(False, *args, **kwargs) 668 669 def exclude(self, *args, **kwargs): /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/query.pyc in _filter_or_exclude(self, negate, *args, **kwargs) 683 clone.query.add_q(~Q(*args, **kwargs)) 684 else: --&gt; 685 clone.query.add_q(Q(*args, **kwargs)) 686 return clone 687 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/sql/query.pyc in add_q(self, q_object, used_aliases, force_having) 1257 else: 1258 self.add_filter(child, connector, q_object.negated, -&gt; 1259 can_reuse=used_aliases, force_having=force_having) 1260 if force_having: 1261 self.having.end_subtree() /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/sql/query.pyc in add_filter(self, filter_expr, connector, negate, trim, can_reuse, process_extras, force_having) 1188 else: 1189 self.where.add((Constraint(alias, col, field), lookup_type, value), -&gt; 1190 connector) 1191 1192 if negate: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/sql/where.pyc in add(self, data, connector) 69 70 if hasattr(obj, "prepare"): ---&gt; 71 value = obj.prepare(lookup_type, value) 72 73 super(WhereNode, self).add( /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/sql/where.pyc in prepare(self, lookup_type, value) 337 def prepare(self, lookup_type, value): 338 if self.field: --&gt; 339 return self.field.get_prep_lookup(lookup_type, value) 340 return value 341 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/fields/__init__.pyc in get_prep_lookup(self, lookup_type, value) 320 return value 321 elif lookup_type in ('exact', 'gt', 'gte', 'lt', 'lte'): --&gt; 322 return self.get_prep_value(value) 323 elif lookup_type in ('range', 'in'): 324 return [self.get_prep_value(v) for v in value] /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/models/fields/__init__.pyc in get_prep_value(self, value) 553 if value is None: 554 return None --&gt; 555 return int(value) 556 557 def contribute_to_class(self, cls, name): ValueError: invalid literal for int() with base 10: 'homework' </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USRyan Saxe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango parameters read in wrong order
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload