use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note: All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note: All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note: All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note: All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note: All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott:

use a default transaction isolation level that isn’t suitable for polling tables for changes. In MySQL the default transaction isolation level is REPEATABLE-READ: meaning the transaction won’t see changes tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. Note: All inspect and control commands supports a --timeout argument ' Examples: # sqlite (filename) result_backend = 'db+sqlite:///results.sqlite' # mysql result_backend = 'db+mysql://scott:tiger@localhost/foo' # postgresql result_backend = 'db+postgresql://scott: