s/DBAPI/DBlib/ On 5/1/07, Rick Morrison <[EMAIL PROTECTED]> wrote: > > The label-truncation code is fine. The issue isn't SA. It's the DBAPI that > pymssql rides on top of...identifier limit is 30 > chars, is deprecated by Microsoft, it will never be fixed. > > Try pyodbc, which has no such limitation. > > > On 5/1/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > > > > > > On May 1, 2007, at 7:50 AM, Graham Stratton wrote: > > > > > > > > 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? > > > > > > > if its the case that MS-SQL allows 128-character column names, but > > only 30 character label names, that would be unfortunate. i might > > have to rewrite the whole label-truncation code (since it cant > > currently differentiate between physical column names and label names). > > > > > > > > >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
