Comments on: Django Schema Evolution

By: Carroll B. Merriman

Carroll B. Merriman — Sat, 06 Mar 2010 19:47:04 +0000

Thanks for your article. I am new at django and this will be a big help.

By: SQL Tutorials

SQL Tutorials — Fri, 01 May 2009 02:11:30 +0000

You know, the thing about SQL is, that there is virtually nothing that can replace it.

Does anyone know if a substitute exists for sql? I mean besides MS SQL and Oracle and all that jazz. Thanks.

By: krl

krl — Thu, 15 May 2008 04:03:14 +0000

I don’t know if you are interested guys but there is an interesting new approach to schema evolution, is called PRISM, developed at UCLA is a tool to support schema evolution in relational DB.

there is a video of th interface here: http://yellowstone.cs.ucla.edu/schema-evolution/documents/Prism-Demo.mov

while from here: http://yellowstone.cs.ucla.edu/schema-evolution/index.php/PrismDemo you can access the on-line demo.

By: » Actualización de Estado de Django: 22 de Julio - Blog de Marcelo Ramos

» Actualización de Estado de Django: 22 de Julio - Blog de Marcelo Ramos — Mon, 17 Dec 2007 02:45:53 +0000

[...] Aparentemente pisándole los talones al proyecto de Mike, Derek Anderson, el autor del proyecto schema-evolution del Summer of Code 2006, ha actualizado su código para que funcione adecuadamente con la versión 0.96 de Django. Derek afirma que el schema-evolution también debería funcionar correctamente con la versión trunk de Django . [...]

By: Zarek

Zarek — Wed, 15 Aug 2007 11:48:27 +0000

This code is very interesting for creating an audit trail for a given model.

http://code.djangoproject.com/wiki/AuditTrail

By: buriy

buriy — Mon, 06 Aug 2007 09:50:47 +0000

Please, patch for django-trunk.
By the way, works perfectly for django-newforms admin!

By: derek

derek — Tue, 31 Jul 2007 18:04:34 +0000

mike, i couldn’t agree more.

By: Mike Heald

Mike Heald — Tue, 31 Jul 2007 09:08:20 +0000

Looks like excellent stuff! Looking closer at what you’re doing here, it looks like our migration projects would actually work very nicely together! A situation where individual developers in a team could use evolution to generate the migrations they need, review them, and then use dbmigration to automatically roll them out to demo/UAT/live servers would be my ideal way of doing things.

By: derek

derek — Mon, 30 Jul 2007 17:12:01 +0000

buriy: fixed this in the schema-evolution branch. (i assume this is where you ran across it, not in the v0.96 patch, right?)

By: buriy

buriy — Sat, 28 Jul 2007 07:34:05 +0000

Don’t work for postgres_psycopg2 backend! If you copy changes from postgres backend, don’t work also.
File “D:\web\projects\ef\manage.py”, line 11, in ?
execute_manager(settings)
File “d:\program\python24\lib\site-packages\django\core\management.py”, line 1952, in execute_manager
execute_from_command_line(action_mapping, argv)
File “d:\program\python24\lib\site-packages\django\core\management.py”, line 1843, in execute_from_command_line
action_mapping[action](int(options.verbosity), options.interactive)
File “d:\program\python24\lib\site-packages\django\core\management.py”, line 793, in syncdb
for sql in get_sql_evolution(app):
File “d:\program\python24\lib\site-packages\django\core\management.py”, line 546, in get_sql_evolution
output = get_sql_evolution_check_for_dead_fields(klass, new_table_name)
File “d:\program\python24\lib\site-packages\django\core\management.py”, line 698, in get_sql_evolution_check_for_dead_fields
suspect_fields.difference_update(f.aka)
TypeError: iteration over non-sequence