Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>+1 on bringing in technologies as you need them. But I understand wanting to be ahead of the curve. I think my answer is really a more verbose version of @cmpolis' comment now that I read all this.</p> <p>You really have two sets of technologies, one for application building, one for application deployment. So being that you don't have to worry much about deployment until you have an application lets set those aside (Fabric, Chef, Puppet, Tornado, and arguably South)</p> <p>You won't get very far building your web app without at least learning some basic of how Postgresql works. You will need to create a database, database user, etc. You don't need to know how to be a wiz, but you need to setup and administer at least a local db.</p> <p>You can't use TastyPie without understanding JSON. You also don't mention how you will be consuming the JSON that TastyPie outputs. (I am going to assume you want TastyPie to do JSON, and not YAML or XML). Do you have a Javascript framework in place for that? If you are going for something like a Tastypie/Backbone stack, I'd focus on that part first, and JSON will come along for the ride. (JSON itself is really trivial to understand). You may want to look at something like <a href="https://github.com/PaulUithol/backbone-tastypie" rel="nofollow">backbone-tastypie</a>. Understanding how to read and write JSON will give you a leg up on understand how to use Redis as well.</p> <p>Learning Jenkins really means just getting it installed and set up. Since Continuous Integration is something easiest implemented at the beginning of a project I would set that up now as well.</p> <p>At that point you will know where you bottlenecks are so I would bring in Celery (and of course <a href="http://ask.github.com/django-celery/" rel="nofollow">django-celery</a></p> <p>So then learn Fabric. I can't really tell if you already know that you will need many, many, servers or if you are speculating. In my opinion, if your configuration is in the single digit number of servers, Fabric may be enough. I would suggest looking at <a href="https://github.com/jacobian/django-deployment-workshop.git" rel="nofollow">Deploying Django Workshop</a> to see how all of these different technologies get tied together.</p> <p>So in short:</p> <p>Phase 1:</p> <ul> <li>Tastypie/JSON</li> <li>Postgresql</li> <li>Celery</li> <li>Fabric</li> <li>Jenkins</li> </ul> <p>Phase 2:</p> <ul> <li>Whatever is left over that you actually need</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POIn what sequence should i learn these technologies for building a web-app using django?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USzenWeasel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIn what sequence should i learn these technologies for building a web-app using django?
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    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