Privacy & Security
Relationship Changes and Your Database
Relationships reviewed, added, edited, or removed in SQL Mocker remain workspace context and do not alter the database.
Steps
1
Import available metadata
Use primary-key and foreign-key relationships already defined by the database where available.
2
Review workspace changes
Add or correct a connection only when the metadata is incomplete or unclear and the relationship can be verified.
3
Use the map as context
SQL Mocker uses reviewed connections when generating multi-table SQL.
4
Apply database changes separately
Creating real foreign keys or constraints requires an authorised database change outside SQL Mocker.
Open the relevant SQL Mocker tool
Continue with this workflow in SQL Mocker when you are ready.