Add SQL migration files for seeding various tables

[drazisil]

Summary by CodeRabbit

• New Features

  • Introduced multiple new tables to manage various aspects of the application, including attachment_point, brand, model, abstract_part_type, part_grade, part_type, branded_part, part, driver_class, player_type, player, skin_type, pt_skin, vehicle, warehouse, login, profile, and key.
  • Established relationships between these tables through foreign key constraints to enhance data integrity.

• Data Seeding

  • Populated several tables with initial data, including attachment_point, brand, abstract_part_type, part_grade, driver_class, player_type, sva_car_class, sva_mode_restriction, stock_vehicle_attributes, skin_type, and others.

• Database Optimization

  • Implemented unique indexes and constraints across various tables to facilitate efficient data retrieval and ensure uniqueness of entries.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Walkthrough

The recent migrations introduce a comprehensive update to the database schema, adding multiple tables for managing vehicle components, user profiles, and attributes. New relationships and constraints enhance data integrity and retrieval efficiency, while seed data populates key tables with initial values. This structured approach improves the overall organization and functionality of the application, setting a solid foundation for future development.

Changes

Files	Change Summary
migrations/0001-createAttachmentPoint.sql migrations/0002-createBrand.sql migrations/0003-createModel.sql	Created tables for attachment points, brands, and models with primary keys, unique indexes, and relevant columns to support structured data management.
migrations/0004-createAbstractPartType.sql migrations/0005-createPartGrade.sql migrations/0006-createPartType.sql	Introduced tables for abstract part types, part grades, and part types, establishing relationships and constraints to ensure data integrity and categorization.
migrations/0007-createBrandedPart.sql migrations/0008-createPart.sql	Added tables for branded parts and parts, incorporating foreign keys for relational integrity along with indexes for optimized queries.
migrations/0009-createDriverClass.sql migrations/0010-createPlayerType.sql	Created tables for driver classes and player types, ensuring unique identifiers with primary keys and unique indexes for efficient data access.
migrations/0011-createPlayer.sql migrations/0012-createSkinType.sql	Established tables for player information and skin types, focusing on attributes relevant to user interaction and customization.
migrations/0013-createPtSkin.sql migrations/0014-createVehicle.sql	Introduced the pt_skin and vehicle tables, detailing attributes and relationships for skins and vehicles, enhancing the gaming context.
migrations/0015-seedAttachmentPoint.sql migrations/0016-seedBrand.sql migrations/0018-seedAbstractPartType.sql	Populated key tables with seed data for initial baseline entries, ensuring essential data availability for application functionality.
migrations/0023-seedDriverClass.sql migrations/0024-seedPlayerType.sql	Added initial entries to driver class and player type tables, enriching the database with necessary classifications.
migrations/0026-createSVACarClass.sql migrations/0027-createSVAModeRestriction.sql migrations/0028-createStockVehicleAttributes.sql	Created tables for car classifications, mode restrictions, and stock vehicle attributes, incorporating indexes and unique constraints to maintain data uniqueness and retrieval speed.
migrations/0038-createWarehouse.sql migrations/0039-createLogin.sql migrations/0040-createProfile.sql	Introduced warehouse, login, and profile tables with relevant attributes and constraints to manage user information and inventory effectively.
migrations/0041-createKey.sql	Created a session key table to associate user profiles with session identifiers, ensuring secure access management through foreign key constraints.

Poem

🐇
In the garden of code where changes bloom,
Tables dance, making room,
Seeds of data, fresh and bright,
Each entry crafted with delight.
From brands to players, all aligned,
A new adventure, well-defined!
🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[deepsource-io]

Here's the code health analysis summary for commits a13bb11..d589a69. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@e842599). Learn more about missing BASE report.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@          Coverage Diff           @@
##             main   #2019   +/-   ##
======================================
  Coverage        ?   9.35%           
======================================
  Files           ?     110           
  Lines           ?    9554           
  Branches        ?     142           
======================================
  Hits            ?     894           
  Misses          ?    8660           
  Partials        ?       0           

Flag	Coverage Δ
cli	9.35% <ø> (?)
connection	9.35% <ø> (?)
database	5.41% <ø> (?)
gateway	41.37% <ø> (?)
mcots	9.35% <ø> (?)
nps	9.35% <ø> (?)
patch	86.08% <ø> (?)
shard	41.47% <ø> (?)
shared	13.44% <ø> (?)
shared-packets	9.35% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.