The problem here is that this works well for small databases, but for
bigger ones it uses too much memory and is a slow process.
On Fri, Jun 10, 2016 at 3:22 PM, Stephen J. Butler wrote:
> I usually just use dumpdata/loaddata to do these kinds of things.
>
> On Fri, Jun 10, 2016 at 12:47 PM, Bru
I usually just use dumpdata/loaddata to do these kinds of things.
On Fri, Jun 10, 2016 at 12:47 PM, Bruno Ribeiro da Silva <
bruno.dev...@gmail.com> wrote:
> Hey guys, I'm not sure if I should be asking this here, but it's related
> to django internals.
>
> I have this idea to create a command th
Hey guys, I'm not sure if I should be asking this here, but it's related to
django internals.
I have this idea to create a command that uses the migrations api to
migrate all the data from one database (eg. MySQL) to another database
(PostgreSQL).
So I would run the migrations in the new targe
Just a note that I open a discussion on making GDAL a hard requirement for
contrib.gis, on the GeoDjango mailing list:
https://groups.google.com/forum/#!topic/geodjango/gD0-1SMOBqU
Feel free to participate in that thread if you have something to say.
Claude
--
You received this message because
Just to update on this, there was some good feedback on the draft for
writing and clarity, and it's now made it into an official draft, located
here:
https://github.com/django/deps/blob/master/draft/0007-official-projects.rst
If you'd like to read through the draft and raise discussion points or
o
