Changes between Version 2 and Version 3 of Ticket #26371


Ignore:
Timestamp:
Mar 17, 2016, 6:28:41 PM (9 years ago)
Author:
Tim Graham
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26371

    • Property Type UncategorizedNew feature
  • Ticket #26371 – Description

    v2 v3  
    55In a "beyond the basics" tutorial section, one chapter might include step by step instructions for moving over to Postgres using Psycopg2, and then using multiple settings files depending on the dev context, and understanding how to navigate this (honestly, I'm not even sure what questions to ask here, because I barely understand how it works).
    66
    7 ETA: correction. On some platforms, it is not possible to deploy with SQLite. Generally speaking, SQLite isn't the favored database for deployed applications.   
     7On some platforms, it is not possible to deploy with SQLite. Generally speaking, SQLite isn't the favored database for deployed applications.
    88
    9  It's very, very easy to make mistakes here, and the documentation for the psycopg2 package itself is inaccurate, and the docs for Postgres are overwhelming.  The combination of Django and Postgres to the new dev feels very, very insurmountable without a pairing buddy.  Please add docs to add  support for this very standard and confusing process.
    10 
    11 
    12 
    13 
    14 
    15 
     9It's very, very easy to make mistakes here, and the documentation for the psycopg2 package itself is inaccurate, and the docs for Postgres are overwhelming.  The combination of Django and Postgres to the new dev feels very, very insurmountable without a pairing buddy.  Please add docs to add  support for this very standard and confusing process.
Back to Top