.. | ||
models | ||
util | ||
batch-logger.js | ||
batch.js | ||
index.js | ||
job_backend.js | ||
job_canceller.js | ||
job_publisher.js | ||
job_queue_pool.js | ||
job_queue.js | ||
job_runner.js | ||
job_service.js | ||
job_status.js | ||
job_subscriber.js | ||
query_runner.js | ||
queue_seeker.js | ||
README.md | ||
user_database_metadata_service.js |
Batch Queries
This document describes the currently supported query types, and what they are missing in terms of features.
Job types
Simple
{
"query": "update ..."
}
Does not support main fallback queries. Ideally it should support something like:
{
"query": "update ...",
"onsuccess": "select 'general success fallback'",
"onerror": "select 'general error fallback'"
}
Multiple
{
"query": [
"update ...",
"select ... into ..."
]
}
Does not support main fallback queries. Ideally it should support something like:
{
"query": [
"update ...",
"select ... into ..."
],
"onsuccess": "select 'general success fallback'",
"onerror": "select 'general error fallback'"
}
Fallback
{
"query": {
"query": [
{
"query": "select 1",
"onsuccess": "select 'success fallback query 1'",
"onerror": "select 'error fallback query 1'"
},
{
"query": "select 2",
"onerror": "select 'error fallback query 2'"
}
],
"onsuccess": "select 'general success fallback'",
"onerror": "select 'general error fallback'"
}
}
It's weird to have two nested query
attributes. Also, it's not possible to mix plain with fallback ones.
Ideally it should support something like:
{
"query": [
{
"query": "select 1",
"onsuccess": "select 'success fallback query 1'",
"onerror": "select 'error fallback query 1'"
},
"select 2"
],
"onsuccess": "select 'general success fallback'",
"onerror": "select 'general error fallback'"
}
}
Where you don't need a nested query
attribute, it's just an array as in Multiple job type, and you can mix objects and
plain queries.