5357f43c35e9cfb7bb2fae897eab6286954865c1 ccpowell Wed Jul 10 11:33:53 2019 -0700 Switching MySQL to MariaDB where appropriate in the documentation, refs #23597 diff --git src/hg/htdocs/goldenPath/help/hgTablesHelp.html src/hg/htdocs/goldenPath/help/hgTablesHelp.html index 1f89cca..3e943ea 100755 --- src/hg/htdocs/goldenPath/help/hgTablesHelp.html +++ src/hg/htdocs/goldenPath/help/hgTablesHelp.html @@ -100,35 +100,35 @@
  • display basic statistics calculated over a selected data set
  • display the schema for table and list all other tables in the database connected to the table
  • organize the output data into several different formats for use in other applications, spreadsheets, or databases
  • This User's Guide is aimed at both the novice Table Browser user as well the advanced user. If you are new to the Table Browser, read the Getting started section to learn about browser basics and try some simple queries. Advanced users may want to proceed directly to the section that addresses a particular area of functionality in detail.

    Although the Table Browser provides sufficient flexibility to satisfy the needs of most users, some -advanced users may require the ability to run MySQL directly on the Genome Browser database. UCSC -provides two public MySQL servers: (1) genome-mysql.soe.ucsc.edu (US West Coast), +advanced users may require the ability to run SQL commands directly on the Genome Browser database. +UCSC provides two public MariaDB servers: (1) genome-mysql.soe.ucsc.edu (US West Coast), (2) genome-euro-mysql.soe.ucsc.edu (Europe). More information can be found on our -MySQL Access page. Alternatively, the database may be -downloaded to a local computer for MySQL access. See the mirror +MariaDB Access page. Alternatively, the database may be +downloaded to a local computer for MariaDB access. See the mirror site documentation for information on setting up a local copy of the database.

    About the Table Browser databases and tables

    The Table Browser is built on top of the Genome Browser database, which actually consists of several separate databases, one for each genome assembly.

    Tables within the databases may be differentiated by whether the data are based on genome start-stop coordinates (positional tables) or are independent of position (non-positional tables).Some output formats and query options are applicable only to positional tables, hence the distinction.