Andrew Ekstedt e6b64b8c5a Relax test for nullability of translation columns ... The previous commit added a nullable subtitle field to location_names. This caused a test in test_schema.py to fail because the name field wasn't also nullable. A comment above the test says, "If there's more than one text column in a translation table they have to be nullable, to support missing translations", but i don't think that logic holds in this case. The idea is that we might have a translation for the subtitle, but not the name, or vice versa, so both need to be nullable in case one or the other is missing. But in this particular case that doesn't make sense: if you don't have a name, you don't have a location; it may or may not have a subtitle, but a location will always have a name. Therefore, add an exception to the test.		2018-09-29 10:12:10 -07:00
..
__init__.py	Modernize our use of py.test	2014-07-06 21:45:05 -07:00
test_database_sanity.py	Addressed all of pyflakes3's complaints	2016-11-24 21:29:58 +00:00
test_docs.py	Add a test for main-tables.rst	2012-06-10 15:46:50 -07:00
test_lookup.py	Fix tests, since Farfetch’d got a name change	2017-09-04 10:04:23 -07:00
test_media.py	Compat with Python 3.3+	2015-10-05 08:12:23 -07:00
test_roomaji.py	Modernize our use of py.test	2014-07-06 21:45:05 -07:00
test_schema.py	Relax test for nullability of translation columns	2018-09-29 10:12:10 -07:00
test_strings.py	Squash a bunch of "non-unicode bind param" warnings	2018-03-30 12:14:55 -07:00
test_translations.py	Compat with Python 3.3+	2015-10-05 08:12:23 -07:00
test_util.py	Squash a bunch of "non-unicode bind param" warnings	2018-03-30 12:14:55 -07:00