Primary key is a tinyint

 We have a table with a pk on a tinyint (SQL 08).  When I drag the table into the designer it says: 

No identity type corresponds to Byte

Is it possible to support this or do we need to change the table (the customer is not keen)?

Thanks

 Oh, dur.  I can do a view I think.

 No, that wont work either cause then I dont get the associations working between entities.

Hmm, that's annoying, I thought we defaulted unrepresentable IDs to Int32 and issued a warning.  I'll see if we can get that fixed for you.

As a workaround, you can always drag on an Entity from the toolbox and create the properties by hand.  (It's safe to use an Int32 identity type, as long as you never actually insert anything with an ID that would overflow tinyint.  I assume this is reference data so this won't be an issue, right?)

Cool, thanks.  I changed the db to int, dragged on the table and will now change the db back to tinyint.  Creating the entity manually would probably be safer tho.

This is LS3 of course.

Cheers

Okay, there's a fix wending its way through the build system.  The LS3 betas aren't getting uploaded automatically at the moment so it may not be available for a couple of days: it sounds like you have a workaround, but if you decide you need the fix, let us know.

(In case anybody else hits this, the fix will also be in LightSpeed 2.2 nightly builds dated 2 Dec 2009 and above.)

 Thanks Ivan, I can wait for the release.

Cheers

With the 8/12 RC I can drag on a table with a tiny int for the pk and it doesnt complain or warn - it just adds an entity with an Int32 instead.  This is good enough for me.

Cheers