dece
0c17bbbc4c
Why ReleaseMetadata and not simply Metadata you ask? Because I want to be sure future entities may have their own type of metadata and not have name conflicts. Why not adding this data to Release? I don't know, I like small tables for the main entities I guess, probably #DoesNotScale.
38 lines
1.4 KiB
PHP
38 lines
1.4 KiB
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
namespace DoctrineMigrations;
|
|
|
|
use Doctrine\DBAL\Schema\Schema;
|
|
use Doctrine\Migrations\AbstractMigration;
|
|
|
|
/**
|
|
* Auto-generated Migration: Please modify to your needs!
|
|
*/
|
|
final class Version20231001125432 extends AbstractMigration
|
|
{
|
|
public function getDescription(): string
|
|
{
|
|
return '';
|
|
}
|
|
|
|
public function up(Schema $schema): void
|
|
{
|
|
// this up() migration is auto-generated, please modify it to your needs
|
|
$this->addSql('CREATE SEQUENCE release_metadata_id_seq INCREMENT BY 1 MINVALUE 1 START 1');
|
|
$this->addSql('CREATE TABLE release_metadata (id INT NOT NULL, release_id INT NOT NULL, year INT DEFAULT NULL, PRIMARY KEY(id))');
|
|
$this->addSql('CREATE UNIQUE INDEX UNIQ_1414EF75B12A727D ON release_metadata (release_id)');
|
|
$this->addSql('ALTER TABLE release_metadata ADD CONSTRAINT FK_1414EF75B12A727D FOREIGN KEY (release_id) REFERENCES release (id) NOT DEFERRABLE INITIALLY IMMEDIATE');
|
|
}
|
|
|
|
public function down(Schema $schema): void
|
|
{
|
|
// this down() migration is auto-generated, please modify it to your needs
|
|
$this->addSql('CREATE SCHEMA public');
|
|
$this->addSql('DROP SEQUENCE release_metadata_id_seq CASCADE');
|
|
$this->addSql('ALTER TABLE release_metadata DROP CONSTRAINT FK_1414EF75B12A727D');
|
|
$this->addSql('DROP TABLE release_metadata');
|
|
}
|
|
}
|