Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are some great solutions here, but I'll like to take it one step further regarding the local file.</p> <p>In a scenario when Google does fail, it should load a local source but maybe a physical file on the server isn't necessarily the best option. I bring this up because I'm currently implementing the same solution, only I want to fall back to a local file that gets generated by a data source.</p> <p>My reasons for this is that I want to have some piece of mind when it comes to keeping track of what I load from Google vs. what I have on the local server. If I want to change versions, I'll want to keep my local copy synced with what I'm trying to load from Google. In an environment where there are many developers, I think the best approach would be to automate this process so that all one would have to do is change a version number in a configuration file.</p> <p>Here's my proposed solution that should work in theory:</p> <ul> <li>In an application configuration file, I'll store 3 things: absolute URL for the library, the URL for the JavaScript API, and the version number</li> <li>Write a class which gets the file contents of the library itself (gets the URL from app config), stores it in my datasource with the name and version number</li> <li>Write a handler which pulls my local file out of the db and caches the file until the version number changes.</li> <li>If it does change (in my app config), my class will pull the file contents based on the version number, save it as a new record in my datasource, then the handler will kick in and serve up the new version.</li> </ul> <p>In theory, if my code is written properly, all I would need to do is change the version number in my app config then viola! You have a fallback solution which is automated, and you don't have to maintain physical files on your server.</p> <p>What does everyone think? Maybe this is overkill, but it could be an elegant method of maintaining your AJAX libraries.</p> <p>Acorn</p>
    singulars
    1. This table or related slice is empty.
    1. POBest way to use Google's hosted jQuery, but fall back to my hosted library on Google fail
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAcorn
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you're doing all that work *just* for jQuery, then I'd say it is overkill. However, if you already have some of those components in place for other pieces of your app (e.g. if you already load scripts from a DB) then it looks pretty nice.
      singulars
      1. PO
      1. USMichael Haren
    2. CO+1 for being thorough and novel, though I'm not convinced the benefit justifies the dev time and complexity.
      singulars
      1. PO
      1. USCory House
 

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