Hi Matt,
It looks nice and the idea is very similar to
https://github.com/festicket/django-migrate-sql. Problems you are noticing
are same as my. Easy tracking Git changes, code reviews, one place where
the final definitions live (like models). It would be nice if Django can do
that.
Petr
Dn
On Wednesday, March 25, 2020 at 1:45:48 AM UTC+10:30, Petr Přikryl wrote:
>
> Hi Adam,
> thank you for your reply.
>
> We usually have few indices, functions and triggers. But the most used
> database object is view. We used them for data synchronizing from some
> third party databases. These d
Hi Adam,
thank you for your reply.
We usually have few indices, functions and triggers. But the most used
database object is view. We used them for data synchronizing from some
third party databases. These databases have complex schema which we want
simplify. So we are building low-level DB API
Hi Petr
I too often end up managing some database objects like triggers, normally
in order to support database migrations. I have always been happy using
RawSQL migration operations though.
What types of database objects are you mostly using? And how?
I think django-migrate-sql is a neat idea, b
I have only proposal for making Django migrations better handling raw SQL
migrations. I like the way how django-migrate-sql do that
https://github.com/festicket/django-migrate-sql. And it would be interested
if Django has this feature build-in.
We use a lot of raw SQL objects in our apps and ti
In our apps we have a lot of database objects which are hard to manage in
classic Django migrations. Next, we clean our migrations time to time to
speed up deployment process. And it would be awesome if Django would have
system for raw SQL "models" and handle migrations and dependencies
automat
