azerothcore / azerothcore/Keira3

[Feature Request] Save as .sql

Open
#401 2 comments 0 reactions 0 assignees View on GitHub
feature request
Dominant language
TypeScript
Stars
450
Forks
183
Avg merge
23h 42m
Merged PRs (30d)
18

Description

It might be cool to have but don't know exactly how it would be done.

Perhaps either:
1. SAI for example: Have an option to save the SAI as "Anachronos - SAI - DATE.sql" or something
2. Have an option to store all changes you make across everything into a file that you then can name whatever you want. For example if you do an update of several things that link together. For example Updating some creature template stuff, some SAI stuff, some Condition stuff etc.

Yea I am a lazy fucker xD Copy pasta takes time :PPP

Amazing work so far btw <3

---
Want to back this issue? **[Post a bounty on it!](https://app.bountysource.com/issues/90922894-feature-request-save-as-sql?utm_campaign=plugin&utm_content=tracker%2F139701226&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://app.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F139701226&utm_medium=issues&utm_source=github).

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. First clarify whether the feature should export one SAI record or capture changes across multiple editor areas, then inspect Keira3’s existing save and database-editing flows. Done should mean an agreed SQL format, a defined naming workflow, and coverage for the selected scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql, typescript
Domain
databases, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.