To add a little more info, 0.3.6 generates: SELECT [T_Event].[EventLastCancellationDate] AS [T_Event_EventLastCancell_8ab9]
whereas 0.3.7 generates [T_Event].[EventLastCancellationDate] AS [T_Event_EventLastCancellationDate] >From what I can find, column names can be up to 128 chars in SQL 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: "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 -~----------~----~----~----~------~----~------~--~---
