Database
This article is for users with advanced needs and introduces database capabilities. If you are just building a showcase website, you can skip this article.
1. Database Capabilities
When You Need a Database
As long as the website needs to save data, a database is needed. Common scenarios:
| Need | Why a Database Is Needed |
|---|---|
| Online booking | Need to save booking records (who, what time, what service) |
| Registration form | Need to save registration information |
| Message / contact form | Need to save visitor-submitted content |
| Member login | Need to save member account information |
| Article / product management | Need to save content entries |
| Orders | Need to save order data |
Conversely, pure showcase websites (content hardcoded on the page, no backend maintenance needed) do not need a database.
Plan Requirements ⚠️
Some plans do not support database use. When AI detects needs involving the database during generation, a popup prompts:
Current plan capability limited The current plan does not support database use. If you need database features, please upgrade to the corresponding plan and then click Continue. You can also choose Continue directly, and the result will be generated without using the database.
You have two choices:
| Choice | Result |
|---|---|
| Upgrade plan | Get full data storage capability; features are truly usable |
| Skip database calls and continue generating | Website pages generate normally, but data cannot be saved |
⚠️ Important judgment: If data storage is core to the business (e.g., a booking system), do not choose skip. After skipping, forms look fillable and submittable, but data will not be saved — this is worse than not having the feature, because you may think you received a customer booking.
Database Space Limit
Database space has a plan upper limit. When exceeded, it prompts:
Database space insufficient prompt This added requirement involves more database space, exceeding the current plan's database space limit. Please upgrade the plan and continue.
Handling methods:
- Clean up unneeded data (e.g., test data, expired records)
- Upgrade to a higher plan
How AI Operates the Database
You do not need to understand database knowledge. Just describe business needs in the AI conversation, and AI will automatically complete table creation and read/write logic. During generation, you will see these actions:
| Display | Meaning |
|---|---|
| Executing SQL statements | Creating tables, modifying table structure |
| Getting table info | Viewing structure of existing tables |
| Getting table data | Reading data in tables |
| Configuring backend services | Building server-side logic for data read/write |
How to Describe Data Needs
A good description lets AI build a reasonable table structure.
❌ Insufficient description
Add a booking feature
✅ Sufficient description
Add an online booking feature. Need to save the following information:
- Customer name (required)
- Phone number (required)
- Booking date
- Booking time slot (morning/afternoon/evening, choose one of three)
- Service item (choose from "Wash & Cut," "Hair Dye," "Perm")
- Remarks (optional)
- Submission time (automatically recorded)
Booking records should be viewable in the backend, filterable by date, and can be marked "Completed."
This way AI can build a complete and usable table and configure the backend management interface.
Viewing and Managing Data
After generation, data can be viewed through two channels:
Channel 1: Management backend (recommended)
Corresponding data table menus will automatically appear in "Management → Content Management," where you can directly add, delete, modify, and query. See the backend "Content Management" for details.
Channel 2: Database login information
The platform provides database connection information, including:
| Field | Description |
|---|---|
| Username | Database login account |
| Password | Database login password |
| Instance ID | Database instance identifier |
| Tenant ID | Tenant identifier |
This is suitable for scenarios requiring direct database connection for batch processing or data analysis.
⚠️ Security reminder: Database credentials are equivalent to full access to data. Please keep them safe and do not spread them in public channels (chat groups, code repositories, documents). If you suspect leakage, please contact customer service promptly.
Frequently Asked Questions
Q: I don't understand databases. Can I still use these features well?
A: Yes. You only need to describe in business language "what information to save," and AI will handle the technical details. Direct database connection is an optional feature for users with technical needs, not mandatory.
Q: I already chose "Skip database." How do I add it back now?
A: First upgrade to a plan that supports the database, then explain in the AI conversation: "I skipped the database before. Now please supplement data storage capability for the booking feature and provide booking record management in the backend."
Q: How do I know whether my form data was actually saved?
A: The most direct method — submit a test record on the frontend yourself, then go to "Management → Content Management" and check whether the corresponding data table has this record. If yes, it was saved.
Q: The database space is full. How do I clean it?
A: In "Management → Content Management," delete unneeded data entries (e.g., test data, expired records). You can also do batch cleanup through direct database connection. Note: deletion operations should be cautious; confirm data is really no longer needed first.
Q: Can I export my data?
A: You can export through direct database connection. Media files support batch export in media management.