From daf209bd6b6fe94cbec162cef2a53c49e9f31cde Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 3 Jun 2016 15:07:14 -0400 Subject: Ensure 'options' is always present in foreign key info Regarding 0e88bcc30ed49193b91f248123f526fa30007f22, "options" needs to be present as a key in the dictionary because Alembic uses this as a guide to know if the backend is even capable of reporting on foreign key options. Change-Id: I271090f75088cfeec24315a878060f9b8a265335 --- lib/sqlalchemy/dialects/sqlite/base.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'lib/sqlalchemy/dialects/sqlite') diff --git a/lib/sqlalchemy/dialects/sqlite/base.py b/lib/sqlalchemy/dialects/sqlite/base.py index 85ebaaa1d..7ddd09993 100644 --- a/lib/sqlalchemy/dialects/sqlite/base.py +++ b/lib/sqlalchemy/dialects/sqlite/base.py @@ -1420,8 +1420,7 @@ class SQLiteDialect(default.DefaultDialect): continue key = keys_by_signature.pop(sig) key['name'] = constraint_name - if options: - key['options'] = options + key['options'] = options fkeys.append(key) # assume the remainders are the unnamed, inline constraints, just # use them as is as it's extremely difficult to parse inline -- cgit v1.2.1