Revision 6366
Added by Aaron Marcuse-Kubitza about 12 years ago
README.TXT | ||
---|---|---|
92 | 92 |
<datasrc> may not contain spaces, and should be abbreviated. |
93 | 93 |
If the datasource is a herbarium, <datasrc> should be the herbarium code |
94 | 94 |
as defined by the Index Herbariorum <http://sweetgum.nybg.org/ih/> |
95 |
Install any MySQL export: |
|
96 |
Create database in phpMyAdmin |
|
97 |
mysql -p database <export.sql |
|
95 |
For MySQL inputs (exports and live DB connections): |
|
96 |
For .sql exports: |
|
97 |
Place the original .sql file in _src/ (*not* in _MySQL/) |
|
98 |
Create a database for the MySQL export in phpMyAdmin |
|
99 |
mysql -p database <inputs/<datasrc>/_src/export.sql |
|
100 |
mkdir inputs/<datasrc>/_MySQL/ |
|
101 |
cp -p lib/MySQL.{data,schema}.sql.make inputs/<datasrc>/_MySQL/ |
|
102 |
Edit _MySQL/*.make for the DB connection |
|
103 |
For a .sql export, use your local MySQL DB |
|
98 | 104 |
Add input data for each table present in the datasource: |
99 | 105 |
For .sql exports, you must use the name of the table in the DB export |
100 | 106 |
For CSV files, you can use any name. It's recommended to use a table |
Also available in: Unified diff
README.TXT: Datasource setup: MySQL inputs: Added steps to export the database to a PostgreSQL-compatible .sql file, which can be directly used by the install process without the need to export each table as CSV