Rick and Michael,

On Feb 11, 2:25 pm, "Rick Morrison" <[EMAIL PROTECTED]> wrote:
> SQLAlchemy assumes that an integer primary key is of the auto-incrementing
> type, and for MSSQL this means IDENTITY_INSERT.
>
> To tell it to not make that assumption, use the autoincrement=False on the
> column:
>
>      ...
>      Column('dateworked', String(10), primary_key=True),
>      Column('empid', Integer, primary_key=True, *autoincrement=False*),
>      Column('reg', Float),

That worked perfectly. And thanks goes out to Micheal for giving such
a thorough explanation of why this needs to be set that way.

>      ...
>
> Your multi-column primary key def looks fine.
>
> Rick

I'm glad I got half of it right anyway. Which reminds me, what does
one do if the table you need to work with doesn't have a primary key
at all? Thanks!

Mike
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to [email protected]
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