In Using Disposable in RxJava

disposables.clear() is invoked in onStop()

But in the comment and also Github
`disposab

Is your feature request related to a problem? Please describe.
Provide help in CLI for sub-commands

Describe the solution you'd like
Sub-commands help should describe the sub-command's functionality and options available for the sub-command

Describe alternatives you've considered
N/A

Additional context
See: golang-migrate/migrate#370

I looked at https://github.com/cakephp/phinx/blob/master/docs/en/migrations.rst#custom-column-types--default-values but still can't really figure out how to apply this to generate mysql virtual columns. The example sql would be

ALTER TABLE `t_calendar_sources` ADD `c_flag_deleted` boolean GENERATED ALWAYS AS (IF((json_unquote(json_extract(`c_attr`,'$.deleted'))) = 'true', 1, 0)) VIRTUAL N

sequelize init:models creates a 'models' folder and an index.js file.

What does this do?

How is this intended to be used?

You might consider putting some comments into the file. Would probably save people a lot of hassle trying to figure this out over and over.

Thanks!

We have a switch as [switch]$Enable that should enable the login but it is not actually coded to do anything.

All that is needed would be logic around whether the parameter was passed in, within the process block would be sufficient: Test-Bound Enable will return true if the parameter was properly passed into the function call.

If passed in then the login object has a Enable() method t

Saving "Eager" associations is really one of the core benefits of using an abstraction layer like this.

The documentation for querying structs with associations is OK, but honestly very very little is said about managing the write aspects of this data, so onboarding to pop from the outside, is a real mountain-climb.

I've been debugging this code off and on for hours over the weekend, and to

I encountered a strange bug: I had a space in front of -- migrate:down, and the migration was getting applied, successfully, except that it wasn't being run (silently failing).

This was pretty bad and took a while for me to fix.

We should likely have stricter parsing of the syntax, if this can silently fail

https://www.postgresql.org/docs/current/static/sql-dropindex.html

CONCURRENTLY

Drop the index without locking out concurrent selects, inserts, updates, and deletes on the index's table. A normal DROP INDEX acquires exclusive lock on the table, blocking other accesses until the index drop can be completed. With this option, the command instead waits until conflicting transactions have co

The actual tables are migrating with the same name. Thus for the following csv:
CUSTOMER,Customer,False

The files are turning up in MySQL (from Oracle) as 'CUSTOMER' but then it tries to add indices and FKs to Customer and falls down in a heap.

Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/45471371-table-transform-only-ha

Describe the bug
Currently the options are not mentioned in the docs but shown in the CLI.
See https://github.com/seppevs/migrate-mongo/blob/master/bin/migrate-mongo.js#L45

To Reproduce
Run migrate-mongo --help

Usage: migrate-mongo [options] [command]

Options:
  -V, --version                   output the version number
  -h, --help                      output usag

Maybe we should test a few high level associations just to make sure we understand where we work and may break down one day.

• How to modify a request
• How to modify a response
• Notate that using dates is not a requirement for versioning
• Events