On Wednesday 08 March 2017 03:42:31 Maksym Mospanenko wrote:
> Yes but I have to run on db server directly (via export sqlmigrate).
No, you don't.
> Djando's manage.py can generate sql only for schema migrations
- not
> for RunPython data migrations.
But you're not *creating* migrations,
We don't have access to db server (only via custom django backend driver)
in our configuration (security reasons). So we have to export raw sql for
schema migrations manually and we can't generate sql for data migrations
(because it is python's logic).
вівторок, 7 березня 2017 р. 11:18:01
Yes but I have to run on db server directly (via export sqlmigrate).
Djando's manage.py can generate sql only for schema migrations - not for
RunPython data migrations.
вівторок, 7 березня 2017 р. 13:14:31 UTC+2 користувач Daniel Roseman
написав:
>
> Schema migrations don't run on the
Schema migrations don't run on the database server, they run on the app server
with the rest of your Django code and communicate with the database in exactly
the same way. If you can run Django, you can run migrations.
--
DR.
--
You received this message because you are subscribed to the
On Monday 06 March 2017 15:40:55 Maksym Mospanenko wrote:
> Hello! I want to migrate data with schema migrations but I can't
run
> any python code on database server - only raw sql (postgres).
> How can I move fk column data to m2m table's fk column?
On the server you can run python code:
python
Hello! I want to migrate data with schema migrations but I can't run any
python code on database server - only raw sql (postgres).
How can I move fk column data to m2m table's fk column?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
6 matches
Mail list logo
