The script adds one table by subset previously added to the database and
maps all terms to the closest term within that subset.  The tables are
named "aux_XX_YY_map" where "XX" is the ontology ("GO" or "SO"), and
"YY" is the subset name (e.g., "goslim_goa").

The schema for each of the subset map tables is simply as follows:

  +----------------+------------------+------+-----+---------+-------+
  | Field          | Type             | Null | Key | Default | Extra |
  +----------------+------------------+------+-----+---------+-------+
  | term_id        | int(10) unsigned | NO   | PRI | NULL    |       |
  | subset_term_id | int(10) unsigned | NO   | PRI | NULL    |       |
  +----------------+------------------+------+-----+---------+-------+

... where both fields refers into the 'term' table.

http://www.ebi.ac.uk/GOA/rat_release.html.

(2) Updated URL for downloading GO file. URL is now
http://archive.geneontology.org/latest-termdb/go_daily-termdb.obo-xml.gz.
("lastest-termdb" has been changed to "latest-termdb")

use LIKE.

+  Arg [2]       : (optional) String
+                  The subset within the ontolgy to which the query
+                  should be restricted.  The subset may be specified
+                  as a SQL pattern, e.g., "goslim%".
+
+  Arg [3]       : (optional) Boolean
+                  If true (non-zero), only return the closest
+                  terms.  If this argument is true, and the previous
+                  argument is left undefined, this method will
+                  return the parents of the given term.
+
+  Description   : Given a child ontology term, returns a list of
+                  all its ancestor terms, up to and including any
+                  root term.  Relations of the type 'is_a' and
+                  'part_of' are followed.  Optionally, only terms in
+                  a given subset of the ontology may be returned,
+                  and additionally one may ask to only get the
+                  closest term(s) to the given child term.

Hopefully speeds up the loading of the term table a bit, especially over
a slow link (SSH from home).

number of separate variables.

'term' table.  The SET is hard-coded and needs updating if new subsets
are added :-/ No index yet as I don't know how we're going to use it.