Database Schema

Overview

Plugins can access the database using Prisma client. Each plugin should namespace its tables to avoid conflicts.

Accessing Prisma

import { prisma } from '@aether/database';

// Query data
const entries = await prisma.timerEntry.findMany({
  where: { workUnitId },
});

// Create data
const entry = await prisma.timerEntry.create({
  data: {
    workUnitId,
    startTime: new Date(),
  },
});

Plugin Table Naming Convention

Prefix all plugin tables with plugin_<slug>_:

CREATE TABLE plugin_timer_entries (...);
CREATE TABLE plugin_tasks_items (...);
CREATE TABLE plugin_analytics_reports (...);

Core Schema Reference

Work Units

• workUnits - Main work unit table
• id, name, status, businessType, organizationId, customerId

Customers

• customers - Customer/client table
• id, name, email, organizationId

Organizations

• organizations - Organization/tenant table
• id, name, businessType, premiumTier

Users

• users - User accounts
• id, name, email

Best Practices

• Always filter by organizationId for multi-tenancy
• Use transactions for multi-step operations
• Add indexes for frequently queried columns
• Use foreign keys with CASCADE delete
• Namespace your tables with plugin_ prefix

Next Steps

• Examples