- columns from Alias objects, when used to target result-row columns, must match exactly

  to the label used in the generated statement.  This is so searching for columns in a
  result row which match aliases won't accidentally match non-aliased columns.
  fixes errors which can arise in eager loading scenarios.

1 files changed, 16 insertions, 0 deletions

diff --git a/test/sql/query.py b/test/sql/query.py
index a519dd974..e64425e91 100644
--- a/test/sql/query.py
+++ b/test/sql/query.py
@@ -429,6 +429,22 @@ class QueryTest(PersistTest):
         self.assertEqual([x.lower() for x in r.keys()], ['user_name', 'user_id'])
         self.assertEqual(r.values(), ['foo', 1])
     
+    def test_exact_match(self):
+        """test that an Alias object only targets result columns that were generated
+        from that Alias.   This is also part of eager_relations.py/test_no_false_hits.
+        """
+        
+        users.insert().execute(user_id=1, user_name='ed')
+        users_alias = users.alias()
+        result = users.select().execute()
+        row = result.fetchone()
+        assert users_alias.c.user_id not in row
+        
+        result = users_alias.select().execute()
+        row = result.fetchone()
+        assert users_alias.c.user_id in row
+        
+        
     @testing.unsupported('oracle', 'firebird') 
     def test_column_accessor_shadow(self):
         meta = MetaData(testbase.db)