This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi Guys, I just did a quick search of the forum and couldn't find this problem, so I'll post it. It's not a biggie at all. I created an entity in the designer and set the identity method as IdentityColumn and identitytype as int32 then ran the 'update database...'. This created the table and a foreign key as expected, but the id column was not created as an IDENTITY column, it was just a plain old int. Easy enough to fix, but thought I'd let you know. |
|
|
Yes, this is a known issue. The reason for it is that LightSpeed identity methods are usually defined at the context (database) level rather than the table level, and we don't have that at design time. Admittedly, that actually makes the issue worse rather than better, because it means we expect users of identity columns to use them *everywhere* rather than just on the odd table here and there, which means they'd need to fix up *every* table if doing model-first. So I've logged a feature request for this. Thanks for the feedback! |
|
|
Thanks Ivan |
|
|
Here Here for the feature request |
|