1

I am looking to extend on top of or use an existing tool for the purpose of database migrations. As we have applications in different languages, I need the tool to be language independent. I came across dbmate which solves my use case but Go language and its lack of support for MSSQL had me have it as a last option.

I see that Alembic is widely popular too. Any insights as to how this tool works with non-python applications? If I were to extend it to be language-independent how much effort would that require?

Thanks in Advance!

oyeesh
  • 551
  • 9
  • 21
  • 1
    When using alembic you write your database migration scripts in python, though the application that uses this database can be written in any other language. – Rugnar Jan 31 '20 at 20:18
  • I just want to use raw SQL for writing my migration scripts. I do not want people to learn python just to use this tool. – oyeesh Jan 31 '20 at 20:24
  • Alembic only makes sense for a project already using sqlalchemy. – jordanm Jan 31 '20 at 20:27
  • @jordanm May I know why. If I were to use alembic for my new applications and new databases to start supporting database migrations why is it not a good idea? I am not looking to support legacy applications to move towards this path right now. – oyeesh Jan 31 '20 at 20:36
  • Alembic supports raw sql queries along with pythonic ORM-based. @jordanm you're not right. Alembic benifits from projects that are in python and using SQLAlchemy but it is not mandatory – Rugnar Jan 31 '20 at 21:23

0 Answers0