Fixed

Primary key issue

4 years ago • updated by 4 years ago • 5

A month ago when I generated my SQL it was nice and clear, but now I generate the same SQL for the same table It create different one with out specifying the primary key.

A month ago

Now

the question is does the two lines are equal

CONSTRAINT [PK_BOOKS] PRIMARY KEY CLUSTERED ([ID] ASC)

CREATE CLUSTERED INDEX [PK_BOOKS] ON [Books]([ID] ASC)

I have SQL 2012 and the execution of these line are not equal at all.

Vote

Answer

Fixed

4 years ago

Hi, the new version with bug fix has been rolled.

Thank you for your assistance,

SqlDBM Team

Replies 5
Oldest first
- Newest first
- Oldest first

Started

4 years ago

Dear User,

Thank you for reporting this issue. Actually, this is known bug and we are pushing the fix for it next release (in next couple of days).

This bug happens only in case when user opens existing project and then loads draft (if there is existing draft).

Thank you for reporting and using SqlDBM.

SqlDBM Team

Answer

Fixed

4 years ago

Hi, the new version with bug fix has been rolled.

Thank you for your assistance,

SqlDBM Team

4 years ago

This seems to still be an issue. I cannot generate my SQL with Primary Keys

4 years ago

same with my project

[Test_ID] is set to PK but only gets the index creation. Is this now default behavior for SQLDBM? Many tools need a PK and I would like to have it.

Test snippet from my modell:

CREATE SCHEMA [dbo];
GO

-- ************************************** [dbo].[Test]

CREATE TABLE [dbo].[Test]
(
[Test_ID] int IDENTITY (1, 1) NOT NULL ,
[Name] nvarchar(50) NOT NULL ,

CONSTRAINT [PK_Test] PRIMARY KEY CLUSTERED ([Test_ID] ASC)
);
GO

4 years ago

Dear User,

Sorry for the inconvenience.

Did you try to change Generate Index/As Constraint option in Index Properties panel?

Thanks

Team - SqlDBM

Customer support service by UserEcho