summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoremkael <emkael@tlen.pl>2015-03-04 22:57:43 +0100
committeremkael <emkael@tlen.pl>2015-03-04 22:57:43 +0100
commit1a815e2be0db6688428a15f58cb86fc18be79603 (patch)
tree4b2c4eb220b85148131f5783bdd00cb1f1bb2ace
parent28da8899cd350f1681b1ea4bd56f8dbd43cb100c (diff)
Update README.md
-rw-r--r--import/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/import/README.md b/import/README.md
index 70e6ec5..6573d3a 100644
--- a/import/README.md
+++ b/import/README.md
@@ -35,7 +35,7 @@ If the DB dump is not present, the script attempts to fetch it via [fetcher](../
The `01_integrity_import.sh` script does the heavy lifting of improving the database under the hood, so it could be used with modern RDBMS techniques. Its main purpose is to create indexes and proper foreign keys constraints in the database.
-All the script does is running all the 01?_*.sql scripts against selected database, in alphabetical order (relying on bash wildcard expansion, [which is supposed to guarantee alphabetical order](http://serverfault.com/questions/122737/in-bash-are-wildcard-expansions-guaranteed-to-be-in-order). The SQL scripts are:
+All the script does is running all the `01?_*.sql` scripts against selected database, in alphabetical order (relying on bash wildcard expansion, [which is supposed to guarantee alphabetical order](http://serverfault.com/questions/122737/in-bash-are-wildcard-expansions-guaranteed-to-be-in-order). The SQL scripts are:
* `01a_integrity_fixes.sql` - fixing some of the values which would otherwise conflict with creating foreign key constraints (usually temporarily, since these issues are reported to the upstream Ergast maintainers)
* `01b_indexes.sql` - creating indexes on some of the columns (chosen arbirtarily, but hopefully using common sense)