database
This section lists the Corda CLI
A command line tool that supports various Corda-related tasks, including Corda Package Installer (CPI) creation and Corda cluster management.
database arguments. You can use these commands to manually perform setup actions in the database, as described in the Manual Bootstrapping section.
| Argument | Description |
|---|---|
| spec | Generates the database schema from Liquibase. |
| -c, --clear-change-log | Deletes the changelog CSV in the PWD to force generation of the SQL files. |
| -g, ---generate-schema-sql | The list of schemas to create. Specify schemas in the form schema-type:schema-name, where schema-type is one of the following: config, messagebus, rbac, or crypto. For example, use config:my-config-schema,crypto:my-crypto-schema to create config tables in a schema called my-config-schema and crypto tables in a schema called my-crypto-schema. Any schemas not specified take the default name, which is the same as schema-type. To create schemas using all default names, pass "" as the value. If not specified, the generated SQL files do not create schemas and it is the responsibility of the database administrator to apply these files to the correct schema. |
| -l, --location | The path to write the generated DML files to. |
| --jdbc-url | The JDBC URL of the database. If not specified, the generation runs in offline mode. |
| -p, --password | The database password. |
| -s, --schemas | The list of SQL files to generate. If not specified, files for all schemas are generated. |
| -u, --user | The database user. |
For example, the following command generates the files for all schemas in the directory /tmp/db:
corda-cli.sh database spec -c -l /tmp/db
corda-cli.cmd database spec -c -l /tmp/db
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.