Oh dear, Oracle being awkward again! Maybe you could list and ten recompile
all functions at the end of the handler code?
On Tue, 21 May 2019 at 23:06, Dan Davis wrote:
> Thank you for the review, Adam.
> I like the idea of the post-migrate signal, but it can be complicated, and
> sometimes
Thank you for the review, Adam.
I like the idea of the post-migrate signal, but it can be complicated, and
sometimes doing things in sequence is important:
With Oracle, if function B runs function A (and so on) then after we run:
CREATE OR REPLACE FUNCTION *A*(...)
We would need to, in
Hi Dan,
I think this has not got much of a response because it might be a bit niche
- it really depends where your teams are struggling to use RunSQL.
Looking for other packages at
https://djangopackages.org/grids/g/database-migration/ , nothing seems to
be related. They are all
I am planning an external package to assist my developers in getting their
special-purpose DDL out of the database and into git. Some teams can
handle it, but some teams could use help making sure that they use
operations.RunSQL well and wisely.
My biggest questions about what I'm doing
