HackSoftware/Django-Styleguide
1
1
Fork 0
mirror of https://github.com/HackSoftware/Django-Styleguide.git synced 2024-11-22 09:36:36 +03:00
Code Issues Packages Projects Releases Wiki Activity

Remove the explicit mention of defining a PK using UUID

Browse Source 
- https://github.com/HackSoftware/Django-Styleguide/issues/136
This commit is contained in:
Radoslav Georgiev 2023-10-22 17:34:49 +03:00
parent d7d50a9d93
commit 645c7214b8
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -221,8 +221,6 @@ It's a good idea to define a `BaseModel`, that you can inherit.
Usually, fields like `created_at` and `updated_at` are perfect candidates to go into a `BaseModel`.
Defining a primary key can also go there. Potential candidate for that is the [`UUIDField`](https://docs.djangoproject.com/en/dev/ref/models/fields/#uuidfield)
Here's an example `BaseModel`:
```python