Dbdiagram.io DBML Syntax Update - Supports Unique, Primary Key, Null/Not Null

DBML Syntax
1

DBML Syntax Update - Supports Unique, Primary Key, Null/Not Null. Please check our release notes for more details

Inline References for foreign keys (Inline Relationships)

Supports unique, primary key, null and not null

2

Hi Anthony,

is it possible to visualize “not null” on the db diagram? Currently I don’t see any impact of this constraint.

Regards
Slavik

3

Hi Slavsla,

We only support them for import/export feature, however, this is a great suggestion, we have added it to our backlog and will think about how to make it better.

Thanks,
Anthony

4

The links from anthony.do appear to be phishing links.

5

Thank you for reporting the problem, @Go_Ideal_Software.

We updated the outdated links.

6

Update July 2023: This feature has been developed and released. Please see below for the official announcement. Thank you.

7

Good to know, thank you! :+1:

1 Like
8

So we cant change PK name?

9

Hi rolivares,

So we cant change PK name?

Unfortunately, no. In theory, you could define the PK constraint as in an index and give a name to it like this:

Table "test_table" {
  "name" varchar [not null]
  "id" varchar
  "linked_name" varchar [not null]

Indexes {
  (id) [pk, name: "test_table_pk"]
}
}

However, there’s currently a bug that prevents the index pk setting from being used together with other settings such as name. We will fix this soon and after that, you can use this scheme to name pk constraints in dbml.

I hope this helps.

Thanks.

10

ok, I’be checking that correction. Thanks

11

Hi Phuc_Nguyen,
Is it fixed ?

12

Hi @Ricky_Huang,

After some testing, I believe we have fixed this (at least in my provided example) following our DBML parser reworks.

Please let know if you encounter any issue naming the PK constraint.

Thanks

13

Hi Phuc_Nguyen,

Sorry for my question is not clear.
Has this feature “change PK name” been fixed ?
I exported to oracle SQL but it still didn’t produce the pk name I specified.

14

Hi @Ricky_Huang,

Indeed, we’re currently not exporting the PK constraint name in DBML to SQL in all of our SQL exporters. I will notify the team of this and let you know when it’s fixed.

Thank you for bringing this to our attention.

1 Like