#32672: Primary Key, type double and type unsigned integer ain't detected
correctly
for Sqlite3 Database
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
juliangrube1988 |
Type: Bug | Status: new
Component: Database | Version: 3.2
layer (models, ORM) | Keywords: SQLite3 PrimaryKey
Severity: Normal | Datatypes
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
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`) )
--
Ticket URL: <https://code.djangoproject.com/ticket/32672>
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/058.972ab0bd3323386df13af381b5b88fa8%40djangoproject.com.
