[TODO] [feature]: SQLite 3 Databases

[gbowne1]

Is your feature request related to a problem? Please describe.

To build our social media app or website, we will likely need several databases, schemas, and tables to handle various aspects of the application. Here are some common components that you might need to consider:

• User Database:
  This database will store user-related information such as usernames, passwords, email addresses, profile details, and authentication tokens.You can have a "Users" table that includes columns like name, email address, phone number, avatar, and social media handles.It's important to ensure the security of user data by properly encrypting passwords and implementing authentication mechanisms.

• Authentication and Authorization:
  we may need a separate database or tables to handle authentication and authorization.This can include tables for storing login credentials (username, password hash, salt), access tokens, refresh tokens, and roles/permissions.You can design tables to link users with their login credentials and associate roles/permissions with specific users.

• Posts and Content:
  To manage posts, comments, and other content shared on the platform, you will need tables to store this information. We can have a "Posts" table with columns like post ID, user ID, content, timestamp, and any other relevant attributes.Additionally, you might need tables for comments, likes, shares, and other interactions related to posts.

• Relationships and Connections:
  Social media apps often involve relationships between users, such as following, friend requests, and connections.You can have tables to represent these relationships, such as a "Followers" table that maps user IDs to the users they are following.Consider using a graph database or a specialized graph modeling technique to efficiently handle and query these relationships.

• Notifications and Messaging:
  If your social media app includes notifications or messaging features, you will need tables to store this data.You can have tables for notifications, messages, conversations, and user-to-user interactions.Design the schema to efficiently handle real-time updates, message threading, and tracking read/unread status.

• Analytics and Metrics:
  To gather insights and track user behavior, you might want to consider incorporating analytics and metrics into your database design.This can involve tables to store data such as user activity, engagement metrics, page views, and other relevant analytics data.

Describe the solution you would like

This is a todo action item.

Describe the alternatives you have tried

MongoDB, Sequelize, Prisma, PostgreSQL.

We are using SQLite 3 for development.

Additional context

No response