Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your question should not be "should I use jQuery or plain JavaScript" but rather "which library should I use?". No one should be starting a substantial project with zero code, they should have at least a good collection of robust, tested code that can easily be collated into a library or tool kit.</p> <p>The problem with a general library is that it must provide general solutions, hence why jQuery has 4,000 lines of code that any one project might only really need a few hundred lines of. Some libraries have very many more lines of code. If you use someone else's library, you are often bound to their update schedule and may well end up using plugins that require different versions of the library.</p> <p>If you have your own library, or one developed and maintained in your work area, you get the same reuse of code and can cut your cloth to suit the project. jQuery (and most general libraries) are monolithic: it's all or nothing, you can't include just one part or another (e.g. you might just want a good <em>addListener</em> function). Your own library can be modular, so you only include the code you need and can avoid many of the cross–browser issues that general libraries must deal with. David Mark's "MyLibrary" is one of the very few modular libraries.</p> <p>Also, cross–browser differences are becoming less and less of an issue and the DOM API is becoming richer so there is less and less need to use a general library. E.g. no one accounts for <em>document.all</em> anymore, or bothers with browsers that don't support either <em>addEventListener</em> or <em>attachEvent</em>. Once support for IE 6 and 7 can be dropped (a few years yet) there will be very little reason to use a monolithic third party library, modularity will be the key. Everything will be a plugin, there will be no need for a base library, or the base library will be very small to provide a generic API for basic DOM functions. </p>
    singulars
    1. This table or related slice is empty.
    1. POReason for using jQuery over javascript besides less code?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRobG
    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. This table or related slice is empty.
    1. COWhile "no one should be starting a substantial project with zero code" holds a certain value, there is **much less** value in people *learning* jQuery, and knowing nothing of JavaScript. This basically leads to programmers not knowing how the internals of JavaScript work, and thus posting questions such as *"OMG! Why doesn't `$('#myDiv') == $('#myDiv')`????"*. There's **always** value in starting from zero at some point; especially since the OP is just starting.
      singulars
      1. PO
      1. USJesse
    2. COThank you very much for taking the time to write all that. I really like your idea of creating ones own library for their specific need in whatever project they are currently working on. It makes a lot of sense and will definitely be heeding your advice. Thanks once again for taking the time to write all that
      singulars
      1. PO
      1. USHate Names
    3. COIncidentally, the concept that "less code is better" is flawed. "Less code" is not a good reason, on it's own, to do anything. It should be the least of your concerns, particularly where a minimiser will be used. "Less code" is often harder to debug and maintain, as is the chaining of function calls common to many libraries. A very long time ago estimates of software development effort focused on functionality, not lines of code, a focus that hasn't changed, particularly as cutting code is probably less than 20% of the overall cost of a software development project.
      singulars
      1. PO
      1. USRobG
 

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