530b00bd76
Instead of having the parser set the defaults, the command will set the defaults so that the constants for that are actually used. This way we can also identify which things the user provided and which ones we are filling with default values. This allows the meta client to be able to make smarter decisions when determining if the user requested a conflict or if the requested capabilities match with what is currently available. If you just say `CREATE DATABASE WITH NAME myrp`, the user doesn't really care what the duration of the retention policy is and just wants to use the default. Now, we can use that information to determine if an existing retention policy would conflict with what the user requested rather than returning an error if a default value ever gets changed since the meta client command can communicate intent more easily. |
||
|---|---|---|
| .. | ||
| internal | ||
| client.go | ||
| client_test.go | ||
| config.go | ||
| config_test.go | ||
| data.go | ||
| data_test.go | ||
| errors.go | ||
| file_unix.go | ||
| file_windows.go | ||
| meta_test.go | ||
| query_authorizer.go | ||
| write_authorizer.go | ||