SA is now doing no column truncation for MS-SQL, as we have not placed any limit within the MS-SQL dialects. previously, SA was truncating all identifiers to 30 characters for all dialects (including those that had much larger limitations), and it would search for these truncated names in result sets.
so this seems to be something happening with the DBAPI itself. if you want to do us a favor and attempt your query with the raw DBAPI, and then look at cursor.description, we can confirm that it is truncating to 30 characters and we can place this number within the corresponding dialect so that both sides agree. if it is the case that MS-SQL overall has a 30 character restriction you might want to consider shortening your column names. On May 1, 2007, at 3:45 AM, Graham Stratton 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: "Could not locate column in > row for column 'Column(u'EventLastCancellationDate',MSDate())'" > > Is this a problem with the changes in 0.3.7 ? > > I'm using pymssql 0.8.0 with SQL server 2000. > > Thanks, > > Graham > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
