Multi Schema

1. Project Based Data Management

To manage multiple projects, it is important that each project has its own data structure. Using Multi Schema, you can create a separate schema for each project and manage project-specific data in isolation. Multi Schema prevents data confusion and enables reports and analysis specific to the needs of your projects. For example, when a software development company develops custom applications for different customers, they can create a separate schema for each customer and manage the data of the projects independently.

2. Large Scale Applications

Large-scale applications often involve a large number of users and data sources. With Multi Schema, it becomes possible to create customized data structures for different user groups in these applications. Each user group can access only relevant data using its own schema. For example, an e-commerce platform can create custom database structures for different user segments (e.g. wholesalers and retail customers). Wholesale buyers can only access data on large orders, while retail customers can only see their own orders.

3. Development and Production Environments

During the development process, it is critical for developers to distinguish between test data and real data. Using Multi Schema, different schemas can be created for the development and production environments of an application, eliminating the risk of mixing test transactions with real data. For example, a mobile app developer can use a separate schema to test the Beta version of the app.

4. Data Backup and Recovery

By using Multi Schema, you can make your data backup and recovery processes more efficient. By managing each schema with different backup policies, you can protect your critical data and recover it quickly when needed. For example, a financial institution can differentiate the backup strategy of each by keeping customer data and transaction history in separate schemas.The Multi Schema feature is an important tool in Kuika Platform that makes data management more flexible and effective. You have learned how you can use it in the scenarios mentioned above, in different industries and use cases.

1. Tables

One of the most fundamental components in the use of Multi Schema are tables. Each schema can contain one or more tables to store different data sets. Tables:

• Data Management: Tables created in different schemas store and manage data belonging to a specific data set.
• Association: Tables ensure data integrity by establishing relationships in other tables. For example, a customer table can be associated with an order table to link customer information with order details.

2. Forms
   • Schema Linking: Each form can be linked to a specific schema to save or update data to tables in that schema.
   • User Interface: Forms can be customized to improve the user experience and users can access only relevant data.
3. Reports
   • Data Analytics: Allows users to analyze data from a specific schema. For example, a sales report can be generated using only data from the sales schema.
   • Visualization: Reports are supported with graphs and tables, allowing users to better understand the data.

1. After logging into the Kuika platform, go to the My Apps screen.

2. Then click the CREATE button in the New Project template to define Multi Schema.

3. Select mobile or web application from the modal that opens.

Schema field will be defined automatically.

Once the Multi Schema is created, it cannot be edited again.

1. After logging in to the Kuika platform, go to the Recent Apps screen.

2. From the list of apps that opens, select the app you want to change the schema for.
3. Then click on the three dots on the right side.

4. Select Edit.
5. You can change the schema by changing the application name in the modal that opens.