Database/Object Storage
Can I use SQL with Hexabase
A. SQL is not available in Hexabase. The data report has a dedicated query builder that allows you to search, sort, group, aggregate, etc.
Are transactions possible?
A. Hexabase supports transactionswith the following APIs:
By using this API, it is possible to create and update multiple databases. For information on how to use the transaction function, please refer to this page.
Can I select from other masters to input fields?
A. Available for database reference type fields.
Is exclusive control possible with Hexabase?
A. Yes, It is possible. For more information, please see exclusive control of item updates.
Is lock processing possible with Hexabase?
A. It is currently not supported.
Can I save image files, etc.?
A. Yes, you can use an attachment type field to store them in object storage.
What is the storage capacity for attachment-type files?
A. It depends on the plan. For details, please see object storage in usage plans and prices.
What is object storage used for?
A. It is mainly used to save attached files and image files.
For example, when you save an attachment on the input screen, the attachment goes into a separate storage system.
Currently, a limit is set for each plan. If the limit is exceeded, you will be charged on a pay-as-you-go basis. For details, please see object storage in usage plans and prices.
This is a proprietary database engine, but what is its processing performance?
A. Processing performance is not disclosed, but performance is evaluated using test data of 1 million cases.
Are there any tools to migrate data from existing system databases?
A. Not currently available.
Can I use GraphQL?
Hexabase is working on making its API compatible with GraphQL as a new feature.
This is currently an alpha version, and specifications are subject to change.
Please contact us if you wish to use it.
Are traditional RDB design methods effective? How should I design it?
A. As a general design method, there is no problem with a method similar to RDB, but if you understand the DB structure unique to Hexabase, you will be able to develop a system more efficiently.
For example, if you want to reference multiple master tables linked to a transaction table, it is easier and more efficient to link them using a database reference type field.
In cases where multiple transaction tables are related, it is necessary to design with consideration for the number of related tables and data items. In this case, there are two options: use the API (CreateItem and UpdateItem) to register and update related items while securing transactions, and use the "auto link" function that automatically links data based on pre-related settings.
The former is transaction-secured, but the latter is executed asynchronously, and there may be a time lag of several seconds to several minutes before the data link is created. If you are updating a small amount of related items, you may choose the former, and if you are updating detailed data on several thousand to tens of thousands of items, you may choose the latter.
Either option must be selected, depending on the use case.
How can I create a relationship between multiple transaction tables?
A. Please use the following API options:
- One-to-many and many-to-many transactions Item Actions - ExecuteAction, ExecuteBatchAction
- When quoting master value from the master code LookupField - include_lookups=true
If master data is also defined in related tables, can the related tables be updated when the master data is updated?
A. If the master data is set as a database reference, then updating the master data will also update the referenced tables.
How do I tune my database? Are there any tuning methods available to developers or system operators?
A. Hexabase is mostly managed by our company's team. If you are planning a large-scale operation, please consult us in advance.
Regarding database tuning, indexes can be specified when configuring the database. Indexes use MongoDB functions, and the advantages and disadvantages of indexes are that they are effective for large-scale logins and transactions, just like regular RDBs.
However, it does not support composite keys.
Basically, it is recommended to specify indexes for search keys.