Too aggressive statements spliting in custom sql

[scibi]

Currently django.core.management.sql.custom_sql_for_model splits statements using r";[ \t]*$"

Unfortunately it doesn't work for statements which include ; like PL/PgSQL functions.

[Anssi Kääriäinen]

We need a better way to run custom SQL. I don't believe there is any way to split the SQL correctly, apart of having full parsers for each of the different backends.

For example reliable pre_model_created, post_model_created signals could be useful here. post_syncdb is also issued after flush which makes it unusable.

I am going to mark this wontfix as there isn't much we can do about it.

[Claude Paroz]

I'd still like to commit #4680, but I also admit that it is probably the most we can do without resorting to a full parser.