Proposal: Annotation for DBML about dbml HOT 4 OPEN

Was there any progress on this concept?

from dbml.

Annotations might also help support database migrations #61.

I can imagine a few different annotations for migrations

• Renamed

Table users {
  @Renamed(from="fullname")
  name varchar
}

That way, once a migration command is ran to gennerate a migration script the tool knows not to drop the fullname column and create a new name, but instead to rename it (similarly for tables).

• DropOnMigration

@DropOnMigration
Table something_cache {
   id varchar
   last_updated date
}

Knows to always drop the table (or column) and recreate it on every migration.

• NotARenamed

Table users {
  @Renamed(from="nickname")
  name varchar
  @NotARename
  nickname varchar
}

Allows you when a migration is created to rename nickname into the name column, and then create a new nickname column.

Then once a migration file is created you can go in and strip those annotations.

This is just one idea for how one could better support migrations, but I do like the idea of annotations to be able to extend dbml.

from dbml.

Maybe the dbml toolchain could have some sort of middleware layer where plugins could come in and announce which annotations they hook into and add additional abilities.

from dbml.

bump

from dbml.