USE internationaliser;
/**
  * Context information tied to a specific translation key. It applies to all locales.
  * We don't store images themselves in the database. It is easier to import URLs into the database than
  * images themselves. It also makes for more efficient handling of the same image being used on many
  * translation keys.
  */
DROP TABLE IF EXISTS context;
CREATE TABLE context (
  /**
   * which ResourceBundle this translation belongs to, project/ResourceBundle -- applies to all locales
   */
   uniqueResourceBundleID INTEGER NOT NULL,
   /**
    * the key the Java source program uses to tie together all the translations resounceBundlename.getString( "key" )
    * This is case sensitive. You may use any combination of upper and lower case.
    * You can use any convention you like including adding punctuation characters like . and _
    * to create a hierarchy e.g. SEARCH.RESULTS.WEB.FOUND_DOCUMENTS
    * In the projects table, you can configure a project-wide REGEX
    * that determines if a translationKey is valid.
    * Dots in the key indicate levels of hierarchy.
    */
   translationKey VARCHAR( 100 ) NOT NULL,
   /**
    * URL of png, gif or jpg, showing translation in context.
    * Not a BLOB the image itself.
    */
   contextImageURL VARCHAR(100),
   /**
    * URL of png, gif or jpg, showing thumbnail of translation in context.
    * Not a BLOB the image itself.
    */
   contextThumbnailURL VARCHAR(100),
   PRIMARY KEY( uniqueResourceBundleID, translationKey ),
   FOREIGN KEY( uniqueResourceBundleID ) REFERENCES resourcebundles( uniqueResourceBundleID )
   );
