TEST

Safe Data Access and Database Design

Contents

1. Filter before fetching

Do not retrieve all records and filter them on the application side. Define conditions in the DB query and fetch only the necessary data. This improves both performance and security.

2. Make queries intentional

Use WHERE, SELECT, ORDER BY, and TAKE to clarify who needs the data, which fields are required, how many records to return, and in what order. Good queries reduce waste and help the system scale.

3. Do not trust client userId

A userId sent from the client should not be trusted. The server should get the authenticated user from the session or auth system, then decide what data the user can access.

4. Separate client and server responsibilities

The client should handle UI behavior, such as clicks, inputs, animations, and local state. The server should handle DB queries, authentication, authorization, billing checks, and admin checks.

5. Use relationship tables

Do not store members as a simple array. Use a relationship table like project_members to represent the connection between users and projects.

6. Store relationship meaning

Relationship tables should store not only user_id and project_id, but also fields like role, status, and joined_at. This makes permissions and membership states easier to model.

Summary

Do not fetch data first and decide later. Design access rules, permissions, data amount, and data shape before retrieving records.

Traceraft 1.1.0 Development Log

Update Details

• Added Pro plan system
• Added paid plans
• Adjusted, corrected, and updated the path for the legal page; managed navigation flow
• Made legal adjustments related to the app

This update mainly focuses on preparing Traceraft for paid features and improving the legal/navigation structure around the app. While this isn’t a flashy feature update, it is an important step toward making Traceraft more stable, trustworthy, and ready for future monetization.