From bc8217cd76c73d5cbc8cd21a5e45c9e38037e5a4 Mon Sep 17 00:00:00 2001
From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Fri, 14 Aug 2009 16:54:49 +0000
Subject: [PATCH] add a really contrived test that tests the _already_compiling
 flag.  but this seems silly so far.

---
 test/orm/test_mapper.py | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/test/orm/test_mapper.py b/test/orm/test_mapper.py
index c34ccdbab8..597b0bd566 100644
--- a/test/orm/test_mapper.py
+++ b/test/orm/test_mapper.py
@@ -891,6 +891,24 @@ class MapperTest(_fixtures.FixtureTest):
         eq_(str((User.name.intersects('ed')).compile(dialect=sa.engine.default.DefaultDialect())), "users.name &= :name_1")
         
 
+    @testing.resolve_artifact_names
+    def test_reentrant_compile(self):
+        # this trips the _already_compiling
+        # flag in mapper.compile().  but if the m2.compile is 
+        # changed to m1.compile, you still get a stack overflow.
+        # not sure why the previous use case did it that way (i.e. 
+        # it was declarative compiling a mapper within ForeignKey()).
+        class MyFakeProperty(sa.orm.properties.ColumnProperty):
+            def post_instrument_class(self, mapper):
+                super(MyFakeProperty, self).post_instrument_class(mapper)
+                m2.compile()
+            
+        m1 = mapper(User, users, properties={
+            'name':MyFakeProperty(users.c.name)
+        })
+        m2 = mapper(Address, addresses)
+        compile_mappers()
+        
     @testing.resolve_artifact_names
     def test_reconstructor(self):
         recon = []
-- 
2.47.2