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 release).

Is anyone else using pymssql? Do you have the same problems?  Should
these changes be made on the trunk?

Thanks,

Graham
On May 1, 7:13 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> it is max_identifier_length() on Dialect.
>
> ive also gone and figured out why it is hard to separate the max
> length of columns vs. that of labels...its because of some issues
> that arise with some auto-labeling that happens inside of
> ansisql.py....so its fortunate i dont have to get into that.
>
> On May 1, 2007, at 12:57 PM, Rick Morrison wrote:
>
> > The underlying DBlib limits *all* identifier names, including
> > column names to 30 chars anyway, so no issue there.
>
> > Where does the character limit go in the dialect? Can I follow
> > Oracle as an example?
>
> > On 5/1/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> > On May 1, 2007, at 11:18 AM, Rick Morrison 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.
>
> > OK well, we should put the 30-char limit into pymssql's dialect.
> > however, the way the truncation works right now, its going to chop
> > off all the column names too...which means unless i fix that, pymssql
> > cant be used with any columns over 30 chars in size.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to