Sub command: Custom

Introduction

The custom sub command provides control to the user on how to load the data, the user can generate a file with the plan of how the data will be loaded to the column, the file can then be modified to let the mock tool to know what kind of data needs to be loaded.

Short Hand: The short hand of the schema subcommand is c

Usage

The usage of table subcommand is

[gpadmin@gpdb-m ~]$ mock custom --help
Control the data being written to the tables

Usage:
  mock custom [flags]

Aliases:
  custom, c

Flags:
  -f, --file string         Mock the tables provided in the yaml file
  -h, --help                help for custom
  -t, --table-name string   Provide the table name whose skeleton need to be copied to the file

Global Flags:
  -a, --address string    Hostname where the postgres database lives
  -d, --database string   Database to mock the data (default "gpadmin")
  -q, --dont-prompt       Run without asking for confirmation
  -i, --ignore            Ignore checking and fixing constraints
  -w, --password string   Password for the user to connect to database
  -p, --port int          Port number of the postgres database (default 3000)
  -r, --rows int          Total rows to be faked or mocked (default 10)
  -u, --username string   Username to connect to the database
  -v, --verbose           Enable verbose or debug logging

Example