I came across this bug and reported it here
https://sourceforge.net/tracker/index.php?func=detailaid=2776267group_id=22307atid=374932
Since SQLAlchemy is indirectly affected by this I want to hear your
opinion on this matter and on the fix proposed.
On deadlocks or lock timeouts cursors are not
Geospatial support is definitely an external project in any case.
As soon as something goes in the core, it's now
linked to our release process, I'm getting the tickets and complaints
personally, etc., theres no way a huge subject like geo support
belongs there.
I agree with you that it has
Any update on this?
On Fri, Apr 17, 2009 at 6:07 PM, Michael Mileusnich
justmike2...@gmail.comwrote:
Actually I made a mistake in running some of these py files manually. The
tables exist now and this is what I receive:
2009-04-17 19:04:59,780 INFO sqlalchemy.engine.base.Engine.0x...1230 ()
