G
YouTube TikTok Games
Skip to content

Migrate development data #345

Closed
Closed

Description

@g105b

I'm finding it more and more useful to have some pre-seeded fake data in the database during development, but this sort of data can't end up in a migration.

Would it be a good idea to have a query/_migration/dev directory to apply AFTER the migration completes for the first time (or with --force), that's only applied on development - maybe with a --dev flag?

Activity

  1. added
    enhancementNon-breaking improvements to existing behaviour
    questionUsage questions or clarification requests
    on Mar 16, 2023
  2. added theissue type on Oct 3, 2025
  3. g105b commented on Mar 24, 2026

    @g105b
    MemberAuthor

    Complete #357 first, then having dev-001.sql in the migrations directory won't break anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNon-breaking improvements to existing behaviourquestionUsage questions or clarification requests

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions