Gyxi DB is fast and affordable, but these are hygiene factors and they are unimportant unless Gyxi is also powerful and useful.
This is the role of Gyxi Views.
Saving one or more items in a database is relatively uncomplicated. It gets complicated when having to make complex queries to retrieve that data and that is also where using a database can become slow and thus useless.
That is why there are no queries in Gyxi DB. Instead there are only Views. For any query you want to make against your data in Gyxi DB, you have to define a view. This view will then be like a prepared query. It will contain the right data in the right order, organized in the right way, placed exactly how you are going to use it.
If the view doesn’t match what you want the solution is simple. Create another view.
You can create any view you want, but we did define some typical scenarios or “view types” which make it easy to understand how views work.
In a database, a basic index is when you choose a field in a table and make it fast and efficient to look up data based on that field.
Similar to a basic index, but combines multiple fields into a combined index.
Uses one or more fields to be able to look up (with extreme efficiency) a single item.
Define the order of the view based on a field, either ascending or descending. This can be combined with most other views.
This specialized view will contain a row for every change to your data. This is achieved by setting the partition key to the current partition+id and then the id is set to the timestamp of the change.
You can find partitions in your data through the portal. However, if you need the partitions through your application, then you can make a view for this. Set the partitionKey to “null” and set the id to be the key that contains the partition.
However, if you need this table, it is likely you have a problem with your data structure. Consider contacting us for guidance instead of creating this view.
This view allows you to make any field, containing an array, searchable (again, with extreme efficiency and scalability).
For example, perhaps your items have a an array with one or more categories associated. This view will allow you to search based on those categories.
Makes it possible to search based on the text in a single field on the item.
Saving an item that has a view based on full text search with the text in the preceding paragraph will cost 26 operations.
Looking up in a view with full text search is very efficient and only costs a single operation but saving new items to the view will require it to be indexed and that makes this view relatively expensive.
The good news is that Gyxi DB is very affordable so even if this view is relatively more expensive than other views, it is still far cheaper than alternatives.