Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Frameworks and libraries leave that "20%" you note so that you can build on top of them. If you are finding that you are still working, barebones, at that 80% level every time you need to add a new feature or functionality then you haven't done anything.</p> <p>Personally, I've used many PHP frameworks where I build custom libraries and functionality on top that helps take my projects to that 90-95% level. That difference of 15% of your project is very important. A few examples of that code are things like: utility functions, permission systems, internal apis and template managers (which help render data with your views).</p> <p>As for client side, Javascript, libraries (jQuery, Prototype, Dojo etc.) it sounds like you haven't thought long term. More and more people are realizing they need to start with a strictly Javascript application structure before thinking about which library to use. Libraries provide some standard ways to bind events, select elements, etc. but none seem to really have large scale application logic built in. You need to build that yourself. </p> <p>Loose coupling (or <a href="http://blog.rebeccamurphey.com/pubsub-screencast" rel="nofollow">Pub/Sub</a> - Publish Subscribe) has become really popular and there are some great libraries that help with MVC and view state like <a href="http://benalman.com/projects/jquery-bbq-plugin/" rel="nofollow">jQuery BBQ</a> and <a href="http://documentcloud.github.com/backbone/" rel="nofollow">Backbone.js</a> (like @Raynos suggested). This logic helps you scale and properly manage new functionality in a way that is standard across your app. That said, you should still understand and begin with a purely library-less application structure you understand. I've written a good <strong>101</strong> post about this here (<a href="http://darcyclarke.me/development/javascript-applications-101/" rel="nofollow">http://darcyclarke.me/development/javascript-applications-101/</a>) and <strong>Addy Osmani</strong> also gives great resources for this here (<a href="http://addyosmani.com/blog/large-scale-jquery/" rel="nofollow">http://addyosmani.com/blog/large-scale-jquery/</a>). A bit different then server-side, I suggest that you build that 15-20% before you dive into the decision of which library to use. They do, after all, have many of the same features and shouldn't be relied on solely to build your client side app.</p> <p>I still think you're better off having these tools in place, rather then building your own from scratch, but I think you need to start building your own set of tools on top of them.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do you grow beyond web frameworks to create your own application framework?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdarcy
    1. USdarcy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COI would argue that viewstate management like `jQuery BBQ` really aught to belong on your server-side.
      singulars
      1. PO
      1. USRaynos
    2. CODepends on what kind of application you're building. Things like SproutCore, jQuery BBQ and Backbone.js all deal with viewstate utilizing hash urls (or 'hashbangs'). With Twitter and Gawker adopting this hashbang approach you'll start to see viewstate management being pushed to the client side more and more. I do suggest having a backup/serverside version of the viewstate available to be used for any kind of permalinking or SEO purposes (for the next year, until Google can finally except, render and index JS based apps and hashbangs)
      singulars
      1. PO
      1. USdarcy
    3. COJavascript templating has also gotten extremely popular lately which would be another reason to adopt a more client side management and rendering of the viewstate. Mustache.js (https://github.com/janl/mustache.js/) and the Official jQuery template plugin (http://api.jquery.com/category/plugins/templates/) are just two of the many that have sprouted up. Plus, who doesn't love creating API's to serve up viewstate data to be used internally, client side or by third parties
      singulars
      1. PO
      1. USdarcy
 

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