django-stringfield
A field intended for strings that typically has a length less than 500 characters. django-stringfield tries to not to enforce length on database level if possible but different databases have different limitations. Currently implemented as:
- PostgreSQL
character varying
- MySQL
VARCHAR (65528) [1]
- Oracle
VARCHAR2 (4000)
- SQLite & Other backends
TEXT
Installation
pip install django-stringfield
Usage
You use this just like the normal django.db.models.CharField except that the key word argument max_length works a little differently:
It is optional and defaults to 500
It only enforces max length on the default formfield not on the database.
Example:
# models.py
from stringfield import StringField
class MyModel(models.Model):
name = StringField()
1 maintainer
Metadata
1 maintainer
Release files for django-stringfield 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-stringfield-0.3.0.tar.gz | 4.1 kB | Without provenance | Details |
Release files / django-stringfield-0.3.0.tar.gz
| Download URL | django-stringfield-0.3.0.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d25bdd1438f3e8bc51e97b5f8950a3de4d7944cb3882e2f14893a293881f0501
|
|
BLAKE2b-256 checksum How to use checksums |
fbbc2e01637d7de827567573c9afee05b2d3de07fd2041f57ff2df644f368f8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-stringfield 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
