My experience with GUID PKs is that they almost always cause more troubles than they purport to solve, and 99% of the time a plain Integer PK will work just fine instead. The two rare exceptions are with multi-database synchronization (and even there integer PKs can work fine with an additional 'source' discriminator column) and humungo databases where overflowing a bigint col is a real fear.
If the only role it's going to play is a plain old surrogate key, they're almost always a bad idea. Anyway, you're not the first to ask about them. Trouble is that MSSQL doesn't make it easy to get the new GUID PK after it's been inserted. If you know the magic words to get MSSQL to cough up an auto-inserted GUID PK, then it would be fairly straightforward to add support for them. Rick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
