Improve relationships. Add references between specific fields.
Open
Nobody has claimed this yet.
enhancement
good first issue
PlantUML
- Dominant language
- Rust
- Stars
- 34
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Remove skinparam linetype ortho to make it work properly
Also add next use case: Teble 2 has two FKs to Table B
https://forum.plantuml.net/3636
Example
@startuml
hide circle
!include https://raw.githubusercontent.com/kurotych/sqlant/b2e5db9ed8659f281208a687a344b34ff38129cd/puml-lib/db_ent.puml
table(tableA) {
column(id, "bigint", $pk=true, $nn=true)
column(tableb_id1, "bigint", $nn=true)
column(tableb_id2, "bigint", $nn=true)
}
table(tebleB) {
column(id, "bigint", $pk=true, $nn=true)
}
tableA::tableb_id1 }o--|| tebleB::id
tableA::tableb_id2 }o--|| tebleB::id
@enduml
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the supplied SQL-to-PlantUML example, including two foreign keys from one table to the same target, and review the linked forum discussion for the expected relationship rendering. Done means the orthogonal line setting no longer interferes and both field-specific relationships are represented correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sql
- Domain
- data-visualization, databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100