#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:
Datatypes | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jgr88):
Replying to [ticket:32672 jgr88]:
> While creating models with "inspectdb" i discovered, that there are
currently some issues with SQLite3 Databases.
> - PrimaryKeys ain't detected properly
> - Datatype double ain't detected properly
> - Datatype unsigned int ain't detected properly
>
> Reproduce these issues by creating a SQLite3 Database:
> CREATE TABLE "test" ( `pId` INTEGER NOT NULL, `doubleField` DOUBLE NOT
NULL, `uInt` UNSIGNED INTEGER NOT NULL, PRIMARY KEY(`pId`) )
>
> I added a pullrequest:
> https://github.com/django/django/pull/14293
Update:
I added [https://github.com/django/django/pull/14297] since i messed up
the first one
--
Ticket URL: <https://code.djangoproject.com/ticket/32672#comment:3>
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.f5602f944e6501272ec8bc1c7ed8a03e%40djangoproject.com.
