At the heart of every Tadabase application is its data structure. Understanding how to organize and structure your data is the foundation of building powerful, efficient applications. This section will teach you everything you need to know about tables, fields, and records.

Data tables are containers that organize related information. Think of them like spreadsheet tabs or file folders - each table holds a specific type of information.

For example, in a CRM application, you might have:

• Contacts table - Stores information about people
• Companies table - Stores information about organizations
• Deals table - Stores information about sales opportunities
• Tasks table - Stores information about activities and to-dos

Each table holds a specific type of entity or object. This separation keeps your data organized and makes it easier to manage, search, and report on.

Think of a data table like a spreadsheet:

• Columns = Fields (define what information you track)
• Rows = Records (individual entries)
• Tab = Table (groups related information)

But unlike spreadsheets, Tadabase tables are far more powerful:

• Enforced data types (dates must be dates, numbers must be numbers)
• Data validation rules
• Automatic calculations
• Relationships between tables
• Advanced querying and filtering
• Scalability to millions of records

Every table has:

• Table Name - Descriptive name (e.g., "Contacts", "Orders", "Projects")
• Fields - Define what information the table stores
• Records - The actual data entries
• Settings - Configuration options for behavior
• Permissions - Control who can view/edit data

Fields define the types of information you track in each table. They're like the columns in a spreadsheet, but much more sophisticated.

A field is a single piece of information you want to store. For example, in a Contacts table, you might have fields for:

• First Name
• Last Name
• Email Address
• Phone Number
• Company
• Date Added
• Status

Tadabase offers 40+ field types. Here are the most common ones you'll use in Phase 1:

Basic Text Fields

• Short Text - Single line of text (names, titles, short notes)
• Long Text - Multiple lines of text (descriptions, comments)
• Email - Email addresses with validation
• Phone - Phone numbers with formatting
• URL - Website addresses

Number Fields

• Number - Numeric values (quantity, age, score)
• Currency - Money amounts with currency symbols
• Percentage - Percentage values
• Auto Increment - Automatically generated sequential numbers

Date & Time Fields

• Date - Calendar dates
• Date & Time - Date with specific time
• Time - Time only (without date)

Selection Fields

• Dropdown - Choose one option from a list
• Multi-Select Dropdown - Choose multiple options
• Radio Buttons - Choose one option (displayed as buttons)
• Checkboxes - Choose multiple options (displayed as checkboxes)

Special Fields

• File Upload - Attach files and documents
• Image - Upload and display images
• Yes/No - True/false or on/off values
• User - Link to application users

Each field has properties you can configure:

• Field Name - Internal identifier (lowercase, no spaces)
• Display Name - What users see
• Description - Help text for users
• Required - Must have a value
• Unique - No duplicate values allowed
• Default Value - Pre-filled value for new records
• Validation Rules - Custom requirements

Selecting the correct field type is important because it affects:

• Data Validation - Ensures data is entered correctly
• Display Format - How data appears to users
• Calculations - What operations you can perform
• Sorting & Filtering - How you can organize data
• Component Compatibility - What components can use the field

Examples of choosing field types:

• Email addresses → Use Email field (validates format, allows email sending)
• Prices → Use Currency field (formats with $, allows calculations)
• Status → Use Dropdown field (limits to predefined options)
• Notes → Use Long Text field (allows multiple lines)
• Quantity → Use Number field (allows math calculations)

Records are the actual data entries in your tables - the individual items you're tracking.

A record is a single entry in a table, like a row in a spreadsheet. Each record contains values for all the fields defined in that table.

For example, in a Contacts table, one record might be:

• First Name: John
• Last Name: Smith
• Email: john.smith@example.com
• Phone: 555-1234
• Company: Acme Corp
• Status: Active

Every record has a unique identifier called the Record ID:

• Automatically generated when record is created
• Never changes
• Used internally to track and link records
• Ensures each record can be uniquely identified

Records can be created several ways:

• Manually - Users enter data through forms
• Import - Upload from CSV or Excel files
• API - Programmatically via REST API
• Rules - Automatically created by automation rules
• Webhooks - Created from external systems

In the Data Builder, you can view all records in a table:

• Table view (like a spreadsheet)
• Search and filter records
• Sort by any field
• Edit records directly
• Bulk operations (delete, update multiple)

Understanding how tables, fields, and records work together is crucial:

The Hierarchy

1. Tables contain fields and records
2. Fields define what information each record stores
3. Records are individual entries with values for each field

A Simple Analogy

Think of tables like a filing cabinet:

• Filing Cabinet = Your Database
• Drawers = Tables (Contacts, Companies, Orders)
• File Folders = Records (each person, each company, each order)
• Information on Folder Labels = Fields (Name, Email, Phone)

Tables Working Together

Tables can be connected through relationships. For example:

• A Contact works at a Company
• A Deal is associated with a Contact
• An Order contains multiple Products
• A Task is assigned to a User

We'll cover relationships in detail in Phase 2, but it's important to understand that tables don't exist in isolation - they work together to model real-world scenarios.

Before creating tables in Tadabase, take time to plan your data structure. Good planning saves time and prevents headaches later.

Identify Your Entities

Start by listing the main "things" you need to track. These become your tables.

Ask yourself:

• What are the main objects or entities in my system?
• What information do I need to store?
• What are people, things, or events I need to track?

Examples:

• CRM: Contacts, Companies, Deals, Activities
• Project Manager: Projects, Tasks, Team Members, Time Logs
• Inventory: Products, Orders, Customers, Suppliers
• Event Management: Events, Attendees, Sessions, Venues

Identify Attributes

For each entity, list what information you need to know. These become your fields.

For a Contact, you might need:

• Name (first and last)
• Email address
• Phone number
• Company
• Job title
• Address
• Status (active/inactive)
• Notes
• Date added

Avoid Redundant Data

Don't repeat the same information in multiple places. Instead, use relationships.

Bad Example:

• Storing company name, address, phone in every contact record

Good Example:

• Create a Companies table
• Link contacts to companies
• Company info stored once, shared by all contacts at that company

Start Simple

Don't try to plan everything upfront:

• Start with core tables and fields
• Build and test
• Add complexity as needed
• Iterate based on actual usage

Tadabase is flexible - you can always add fields, create new tables, and adjust as you learn.

Follow these best practices to create well-structured, maintainable databases:

Naming Conventions

• Table Names: Use plural nouns (Contacts, Orders, Projects)
• Field Names: Use descriptive names (first_name, not fn)
• Be Consistent: Use same naming style throughout
• Avoid Spaces: Use underscores (order_date, not "order date")
• Be Descriptive: Clear names are better than short ones

Table Organization

• One table per entity type
• Keep related information together
• Don't create tables for every tiny detail
• Group logically related tables

Field Organization

• Put most important fields first
• Group related fields together
• Use appropriate field types
• Make required fields truly necessary
• Provide helpful descriptions

Data Validation

• Use field type validation (email format, number ranges)
• Set required fields for critical data
• Use unique constraints where appropriate (email, SKU)
• Provide default values when sensible
• Use dropdown lists to limit options

Scalability Considerations

• Think about future growth
• Design for thousands of records, not just dozens
• Use indexed fields for frequently searched data
• Avoid overly complex structures initially

Now let's create a table in Tadabase. We'll create a simple Contacts table.

Step 1: Access Data Builder

1. Open your application in the builder
2. Click on "Data Builder" in the left sidebar
3. You'll see an empty canvas (no tables yet)

Step 2: Create New Table

1. Click the "+ Create Table" button
2. Enter table name: Contacts
3. Optionally add a description: "Store contact information"
4. Click "Create"

Step 3: Table Created

Congratulations! You've created your first table. Tadabase automatically creates a few default fields:

• Record ID - Unique identifier for each record
• Date Created - When the record was created
• Date Modified - When the record was last updated

These system fields are created automatically for every table and don't count toward your field limits.

Now let's add custom fields to store the information we need.

Adding a Short Text Field

1. Click "+ Add Field" button
2. Select "Short Text" field type
3. Enter field name: first_name
4. Enter display name: First Name
5. Check "Required" (make it mandatory)
6. Click "Save"

Add More Fields

Repeat the process to add these fields:

Last Name (Short Text)

• Field name: last_name
• Display name: Last Name
• Required: Yes

Email (Email)

• Field name: email
• Display name: Email Address
• Required: Yes
• Unique: Yes (no duplicate emails)

Phone (Phone)

• Field name: phone
• Display name: Phone Number
• Required: No

Company (Short Text)

• Field name: company
• Display name: Company
• Required: No

Status (Dropdown)

• Field name: status
• Display name: Status
• Options: Active, Inactive, Prospect
• Default: Active
• Required: Yes

Notes (Long Text)

• Field name: notes
• Display name: Notes
• Required: No

Now that your table has fields, let's add some data.

Accessing Records View

1. Click on your Contacts table in the Data Builder
2. Click the "Records" tab at the top
3. You'll see an empty table (no records yet)

Adding a Record Manually

1. Click the "+ Add Record" button
2. A form appears with all your fields
3. Fill in the information:
   • First Name: John
   • Last Name: Smith
   • Email: john.smith@example.com
   • Phone: 555-1234
   • Company: Acme Corp
   • Status: Active
   • Notes: Met at conference
4. Click "Save"

Viewing Records

Your record now appears in the table view. You can:

• Sort - Click column headers to sort
• Search - Use search box to find records
• Filter - Apply filters to show specific records
• Edit - Click a record to edit it
• Delete - Select record and click delete

Editing Records

1. Click on any record to open it
2. Modify the fields you want to change
3. Click "Save" to update

Bulk Operations

You can perform operations on multiple records:

• Check boxes to select multiple records
• Use bulk actions: Delete, Update field values
• Export selected records

Practice Exercise

Add at least 5 more contact records with different information. This will give you data to work with when we create pages in the next section.

Let's explore some commonly used field types in more detail:

Short Text vs Long Text

Short Text:

• Single line input
• Best for: Names, titles, SKUs, brief entries
• Character limit: configurable
• Displays in single line on forms and tables

Long Text:

• Multi-line text area
• Best for: Descriptions, comments, notes, articles
• No character limit (or very high)
• Displays as text box on forms
• Can include rich text formatting (optional)

Dropdown Fields

Use dropdowns when:

• You have a limited set of predefined options
• Want to ensure consistency (no typos or variations)
• Need to filter or group by these values

Examples:

• Status (Active, Inactive, Pending)
• Priority (High, Medium, Low)
• Department (Sales, Marketing, Support)
• Country (list of countries)

Date Fields

Date fields provide:

• Calendar picker for easy selection
• Consistent date format
• Date-based filtering and sorting
• Calculations (days between, add days, etc.)

Use for:

• Birth dates
• Start/end dates
• Due dates
• Event dates

Number Fields

Number fields enable:

• Mathematical calculations
• Aggregations (sum, average, min, max)
• Numeric sorting
• Number formatting (decimals, thousands separators)

Use for:

• Quantities
• Scores
• Ages
• Measurements

Currency Fields

Currency fields are special number fields:

• Automatic currency symbol ($, €, £, etc.)
• Two decimal places
• Proper formatting with commas
• Support for different currencies

Use for:

• Prices
• Costs
• Revenue
• Budgets

Yes/No Fields

Simple boolean (true/false) fields:

• Checkbox display
• Toggle switch option
• Filter by yes or no

Use for:

• Active/Inactive status
• Email opt-in
• Featured items
• Completed tasks

Tadabase automatically creates several system fields for every table:

Record ID

• Unique identifier for each record
• Auto-generated sequential number
• Never changes or repeats
• Used internally for relationships and linking
• You can display it but users typically don't edit it

Date Created

• Timestamp when record was created
• Automatically set
• Never changes
• Useful for sorting by newest/oldest
• Can be used in filters and reports

Date Modified

• Timestamp when record was last updated
• Automatically updated on any change
• Useful for tracking recent activity
• Can be used to identify stale records

Created By & Modified By

• Track which user created/modified the record
• Available in apps with user authentication
• Useful for audit trails
• Can be used for security rules

You can modify your table structure at any time:

Adding New Fields

• Click "+ Add Field" anytime
• New field is added to all existing records (empty until filled)
• Set default values to populate existing records

Editing Fields

• Click field name to edit properties
• Change display name, description, settings
• Be careful changing field type (may lose data)

Deleting Fields

• Click field options → Delete
• Warning: Deleting fields permanently removes all data in that field
• Tadabase will prompt for confirmation

Reordering Fields

• Drag and drop fields to reorder
• Changes order in forms and tables
• Put most important fields first

Before moving to the next section, ensure you understand:

• What tables are and how they organize data
• What fields are and how they define information types
• What records are and how they store actual data
• How to create a new table in Tadabase
• How to add fields to a table
• How to choose appropriate field types
• How to add and edit records manually
• The difference between system fields and custom fields
• Best practices for naming and organizing tables and fields

You now understand the foundation of data structure in Tadabase. You've created your first table, added fields, and entered records. This is the backbone of your application.

In the next section, you'll learn about pages and components - how to create the user interface that displays and interacts with this data.

Hands-On Exercise (To Be Added)

Exercise placeholders will include:

• Create a Contacts table with all the fields described above
• Add at least 10 contact records with varied data
• Practice editing and deleting records
• Create a second table (Companies) with fields: company_name, industry, website, phone
• Add 5 company records
• Experiment with different field types
• Practice sorting and filtering records

Knowledge Check (To Be Added)

Quiz questions will test understanding of:

• Difference between tables, fields, and records
• When to use different field types
• Best practices for table design
• How system fields work
• Planning data structures
• Naming conventions