Re: Re[4]: [Sqlalchemy-users] CASE in column list

OK, this patch against trunk r#1455 works with your testcase. It defines a new CalculatedClause() class similar to that of Function(), and refactors Function() to derive from this new class. Also adds new visit_calculatedclause() function to handle the compile-time part. It requires the use of l

Re: Re[4]: [Sqlalchemy-users] CASE in column list

seems to work, committed in the trunk + merge to 0.2, test case is test/case_statement.pyOn May 15, 2006, at 7:22 PM, Rick Morrison wrote:OK, this patch against trunk r#1455 works with your testcase. It defines a new CalculatedClause() class similar to that of Function(), and refactors Function()

Re: [Sqlalchemy-users] session context proposal

On May 14, 2006, at 1:42 AM, Daniel Miller wrote: I'm not sure how many (if any) tests this may have broken. I've always had problems trying to run the tests...is there anything special I need to do? Give it a whirl and let me know what you think. not every unit test has been converted to

Re: [Sqlalchemy-users] Thread segmentation fault

Hm, it does fix the errors in my test-programm. However, I'm still getting an anonymous Segmentation Fault in my app with it. I's quite strange. Quoting Michael Bayer <[EMAIL PROTECTED]>: > just did a google for "cx_oracle threadsafe" and came up with this: > > http://mail.python.org/piperm

Re: [Sqlalchemy-users] Thread segmentation fault

just did a google for "cx_oracle threadsafe" and came up with this: http://mail.python.org/pipermail/db-sig/2004-January/003897.html but then there also seems to be a more improved way as of 4.0.1 which is this: http://starship.python.net/crew/atuining/cx_Oracle/html/module.h

[Sqlalchemy-users] Thread segmentation fault

Hi, Selecting from multiple threads with thread-count > 10 my app: * crashes without any error message * starts spweing out cx_Oracle.DatabaseError: Error while trying to retrieve text for error ORA-12520 * crashes with: *** glibc detected *** double free or corruption (fasttop): 0x3eeff0b8 ***

[Sqlalchemy-users] [bug] index name conflicts when two tables have the same column name

The following code doesn't work when sqlite is used as a backend; the unique index on both tables is created with the same name. This is SQLAlchemy 0.1.7 with pysqlite2 2.2.2. from sqlalchemy import * a = Table('a', Column('id', Integer, primary_key=True), Column('name', String, unique=True) )