Change capabilities to uint64_t

- Since the capabilities are a bitmask, it is better if an unsigned
  integral type is used.
- Since the function is part of an ABI, it is better if an explicit
  size is used.
- 64-bits so that there also is room for independent filter
  capabilities.
This commit is contained in:
Johan Wikman
2016-10-20 17:47:00 +03:00
parent d938f0e72f
commit 6bcb3ce4dc
13 changed files with 32 additions and 35 deletions

View File

@ -82,7 +82,7 @@ static void clientReply(ROUTER *instance, void *router_session, GWBUF *queue,
static void handleError(ROUTER *instance, void *router_session,
GWBUF *errmsgbuf, DCB *backend_dcb,
error_action_t action, bool *succp);
static int getCapabilities();
static uint64_t getCapabilities();
/*
* End of the API functions; now the module structure that links to them.
@ -1055,14 +1055,14 @@ lock_failed:
/**
* @brief Get router capabilities (API)
*
*
* Return a bit map indicating the characteristics of this particular router.
* In this case, the only bit set indicates that the router wants to receive
* data for routing as whole SQL statements.
*
* @return int RCAP_TYPE_STMT_INPUT.
*
* @return RCAP_TYPE_STMT_INPUT.
*/
static int getCapabilities()
static uint64_t getCapabilities()
{
return RCAP_TYPE_STMT_INPUT;
}