Opened 4 years ago
Last modified 3 years ago
#32672 closed Cleanup/optimization
Primary Key, type double and type unsigned integer ain't detected correctly for Sqlite3 Database — at Initial Version
| Reported by: | jgr88 | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 3.2 |
| Severity: | Normal | Keywords: | SQLite3 PrimaryKey Datatypes |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
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) )
Note:
See TracTickets
for help on using tickets.