Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Webfaction</strong>:</p> <p>Plus:</p> <ol> <li>Great shell access. Ability to install python modules, or anything else you might need. You will love checking out source code from shell to update your production (no need for FTPing anything anymore!)</li> <li>Very good performance and reliability</li> <li>Great support + wealth of info on help knowledge base and in the forums. (FORGET bluehost or anything else you ever tried). I was surprised by amount of answers I found to what I thought would be difficult questions.</li> <li>You can use regular database and you can do joins (see app engine minus #2)</li> </ol> <p>Minus:</p> <ol> <li>Setting up initial deployment can be a bit tricky the first few times around (as is to be expected from shell).</li> <li>Growing-scaling can be expensive and you probably will not survive beign "slashdotted"</li> </ol> <p><strong>App Engine</strong></p> <p>Plus:</p> <ol> <li>Free to start with</li> <li>Initial database is easier to setup.</li> <li>Deployment is a breeze</li> <li>Enforcement of "good" design principles from the start which help you with #5. (Such as hard limits, db denormalizing etc)</li> <li>Scalability (but this does not come free - you need to think ahead).</li> <li>No maintanence: auto backups, security comes for free, logging + centralized dashboard, software updates are automatic.</li> </ol> <p>Minus:</p> <ol> <li>Setting up Django on App Engine is not so straightforward, as well as getting used to this setup. The webapp framework from google is weak.</li> <li>Database model takes a little bit of time to wrap your head around. THis is not your moma's SQL server. For example you have to denormalize your DB from the start, and you cannot do Joins (unless they are self joins)</li> <li>The usual things you are used to are not always there. Some things such as testing and data-importing are not that easy anymore.</li> <li>You are tied down to App Engine and migrating your data to another DB or server, while not impossible, is not easy. (Not that you do data migration that often! Probably never)</li> <li>Hard limits in requests, responses and file sizes (last time I heard about 1MB).</li> <li>App Engine currently supports Python 2.5 only.</li> </ol> <p>Can't think of anything else so far. I am currently with Webfaction and am testing App Engine as well. I have no difficulty going from Django-Webfaction to App-Engine way of thinking. However, I am not sure if the AppEngine -> Standalone servers route would be just as easy.</p> <p><strong>References</strong></p> <p>Talks:</p> <ul> <li>Guido on Google App Engine <a href="http://www.youtube.com/watch?v=CmyFcChTc4M" rel="noreferrer">http://www.youtube.com/watch?v=CmyFcChTc4M</a></li> <li>Task Queues in App Engine: <a href="http://www.youtube.com/watch?v=o3TuRs9ANhs" rel="noreferrer">http://www.youtube.com/watch?v=o3TuRs9ANhs</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POIs Google App Engine better than Webfaction for a beginner in Django dev?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdrozzy
    1. USdrozzy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs Google App Engine better than Webfaction for a beginner in Django dev?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload