#24371: Recommend that new projects start with PostgreSQL
------------------------------------------------+------------------------
Reporter: carljm | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
A recurring issue on `#django` is users who have built a project locally
using SQLite, and get to the point of wanting to deploy it, and want to
switch to PostgreSQL. This introduces another sometimes-significant hurdle
in their deployment learning curve (which is already unfortunately steep).
In general I think users would be better off if they just started with
PostgreSQL instead.
I don't think it's feasible to change the default project template off of
SQLite, simply because of the "built-in, works out of the box" factor. But
I think we could/should add a call-out to the tutorial, along the lines of
"when starting your first real project, you may want to start out right
away with a production-level database like PostgreSQL, to avoid database-
switching headaches down the road."
--
Ticket URL: <https://code.djangoproject.com/ticket/24371>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.1e74ca4a8fa9e33c6c1683da31cf2f5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
