[sqlalchemy] Re: Column name mapping problem in 0.3.7

2007-06-27 Thread Graham Stratton
than set sane_rowcount to False. Can't remember why now, I'm currently running our local test suite which should remind me. Rick On 6/6/07, Graham Stratton [EMAIL PROTECTED] wrote: I'm bringing this old thread up because I'm still having the same issue with 0.3.8. In order to use

[sqlalchemy] Re: Column name mapping problem in 0.3.7

2007-06-06 Thread Graham Stratton
I'm bringing this old thread up because I'm still having the same issue with 0.3.8. In order to use mssql I have to add def max_identifier_length(self): return 30 to the pymssql dialect. I also find that I need to set has_sane_rowcount=False (as I have had to with every

[sqlalchemy] Precompiling O/RM queries?

2007-05-14 Thread Graham Stratton
Hi, I'm getting some surprisingly poor performance from SQLAlchemy in .get() operations. They're typically taking about 100-200ms, though varying quite a lot. Just doing engine.execute() on the echo()ed SQL takes about 10ms. The query is not small, with a few LEFT OUTER JOINS to eagerly loaded

[sqlalchemy] Re: Precompiling O/RM queries?

2007-05-14 Thread Graham Stratton
do you mean, the compilation of the Select object into a string ? extremely unlikely. the main speed issue with get() is that of fetching rows from DBAPI and processing into object results, which goes up by a huge margin if you have a lot of eagerly loaded instances attached to the get.

[sqlalchemy] Ticket 185-like issues on inheriting from alias in 0.3.7

2007-05-02 Thread Graham Stratton
Hi, Now I've set the maximum identifier length to 30 chars (thanks!), I have a new problem. My Person class inherits from PersonEntry, and the get() method on Person now fails when passed a single id. This seems to be due to the removal of the workaround for #185 in orm.query.Query._get I

[sqlalchemy] Column name mapping problem in 0.3.7

2007-05-01 Thread Graham Stratton
Hi, I've just upgraded to 0.3.7, and when the combined table/column name is at least 30 characters I get an error from the mapper like this: sqlalchemy.exceptions.NoSuchColumnError: Could not locate column in row for column 'Column(u'EventLastCancellationDate',MSDate())' Is this a problem with

[sqlalchemy] Re: Column name mapping problem in 0.3.7

2007-05-01 Thread Graham Stratton
server, but maybe pymssql is truncating at 30? Graham On May 1, 8:45 am, Graham Stratton [EMAIL PROTECTED] wrote: Hi, I've just upgraded to 0.3.7, and when the combined table/column name is at least 30 characters I get an error from the mapper like this: sqlalchemy.exceptions.NoSuchColumnError