Project

General

Profile

« Previous | Next » 

Revision 9492

README.TXT: Full database import: added steps to check that TNRS ran successfully, and fix errors (due to column changes in the TNRS CSV) if it didn't

View differences:

README.TXT
110 110
	In PostgreSQL:
111 111
		Check that the provider_count and source tables contain entries for all
112 112
			inputs
113
	Check that TNRS ran successfully:
114
		tail -100 inputs/.TNRS/tnrs/logs/tnrs.make.log.sql
115
		If the log ends in an AssertionError
116
			"assert sql.table_col_names(db, table) == header":
117
			Figure out which TNRS CSV columns have changed
118
			On local machine:
119
				Make the changes in inputs/.TNRS/schema.sql
120
				rm inputs/.TNRS/tnrs/header.csv
121
				make inputs/.TNRS/reinstall schema_only=1
122
				make schemas/public/reinstall
123
				If there are errors "column ... does not exist", etc.:
124
					Make the necessary changes in schemas/vegbien.sql
125
					make schemas/public/reinstall
126
				make schemas/remake
127
				inputs/test_taxonomic_names/test_scrub
128
				In inputs/test_taxonomic_names/_scrub/TNRS.sql, copy the body of
129
					the "COPY tnrs ..." statement to inputs/.TNRS/data.sql
130
				Commit
131
			On vegbiendev:
132
				If dropping a column, save the dependent views
133
				Make the same changes in the live TNRS.tnrs table on vegbiendev
134
				If dropping a column, recreate the dependent views
135
				Restart the TNRS client: make scrub by_col=1 &
113 136
	tail inputs/{.,}*/*/logs/$version.log.sql
114 137
	In the output, search for "Command exited with non-zero status"
115 138
	For inputs that have this, fix the associated bug(s)

Also available in: Unified diff