#32672: Primary Key, type double and type unsigned integer ain't detected 
correctly
for Sqlite3 Database
-------------------------------------+-------------------------------------
     Reporter:  jgr88                |                    Owner:  jgr88
         Type:  Bug                  |                   Status:  assigned
    Component:  Database layer       |                  Version:  3.2
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  SQLite3 PrimaryKey   |             Triage Stage:  Accepted
  Datatypes                          |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 OK, this seems a reasonable proposal to me.


 Generated model:

 {{{
 class Test(models.Model):
     pid = models.AutoField(db_column='pId')  # Field name made lowercase.
     doublefield = models.TextField(db_column='doubleField')  # Field name
 made lowercase. This field type is a guess.
     uint = models.TextField(db_column='uInt')  # Field name made
 lowercase. This field type is a guess.

     class Meta:
         managed = False
         db_table = 'test'
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32672#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.67d6a6cba8fb7f268daa23a07b221799%40djangoproject.com.

Reply via email to