<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Django Schema Evolution</title>
	<link>http://kered.org/blog/2007-07-19/django-schema-evolution/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Fri, 25 Jul 2008 12:08:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: &#187; Actualización de Estado de Django: 22 de Julio - Blog de Marcelo Ramos</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-15654</link>
		<pubDate>Mon, 17 Dec 2007 02:45:53 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-15654</guid>
					<description>[...] 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 . [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 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 . [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Zarek</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-12204</link>
		<pubDate>Wed, 15 Aug 2007 11:48:27 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-12204</guid>
					<description>This code is very interesting for creating an audit trail for a given model.

http://code.djangoproject.com/wiki/AuditTrail</description>
		<content:encoded><![CDATA[<p>This code is very interesting for creating an audit trail for a given model.</p>
<p><a href="http://code.djangoproject.com/wiki/AuditTrail" rel="nofollow">http://code.djangoproject.com/wiki/AuditTrail</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: buriy</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-12002</link>
		<pubDate>Mon, 06 Aug 2007 09:50:47 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-12002</guid>
					<description>Please, patch for django-trunk. 
By the way, works perfectly for django-newforms admin!</description>
		<content:encoded><![CDATA[<p>Please, patch for django-trunk.<br />
By the way, works perfectly for django-newforms admin!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: derek</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11775</link>
		<pubDate>Tue, 31 Jul 2007 18:04:34 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11775</guid>
					<description>mike, i couldn't agree more.  :)</description>
		<content:encoded><![CDATA[<p>mike, i couldn&#8217;t agree more.  <img src='http://kered.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Heald</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11768</link>
		<pubDate>Tue, 31 Jul 2007 09:08:20 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11768</guid>
					<description>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.</description>
		<content:encoded><![CDATA[<p>Looks like excellent stuff! Looking closer at what you&#8217;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.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: derek</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11749</link>
		<pubDate>Mon, 30 Jul 2007 17:12:01 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11749</guid>
					<description>buriy:  fixed this in the schema-evolution branch.  (i assume this is where you ran across it, not in the v0.96 patch, right?)</description>
		<content:encoded><![CDATA[<p>buriy:  fixed this in the schema-evolution branch.  (i assume this is where you ran across it, not in the v0.96 patch, right?)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: buriy</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11696</link>
		<pubDate>Sat, 28 Jul 2007 07:34:05 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11696</guid>
					<description>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</description>
		<content:encoded><![CDATA[<p>Don&#8217;t work for postgres_psycopg2 backend! If you copy changes from postgres backend, don&#8217;t work also.<br />
  File &#8220;D:\web\projects\ef\manage.py&#8221;, line 11, in ?<br />
    execute_manager(settings)<br />
  File &#8220;d:\program\python24\lib\site-packages\django\core\management.py&#8221;, line 1952, in execute_manager<br />
    execute_from_command_line(action_mapping, argv)<br />
  File &#8220;d:\program\python24\lib\site-packages\django\core\management.py&#8221;, line 1843, in execute_from_command_line<br />
    action_mapping[action](int(options.verbosity), options.interactive)<br />
  File &#8220;d:\program\python24\lib\site-packages\django\core\management.py&#8221;, line 793, in syncdb<br />
    for sql in get_sql_evolution(app):<br />
  File &#8220;d:\program\python24\lib\site-packages\django\core\management.py&#8221;, line 546, in get_sql_evolution<br />
    output = get_sql_evolution_check_for_dead_fields(klass, new_table_name)<br />
  File &#8220;d:\program\python24\lib\site-packages\django\core\management.py&#8221;, line 698, in get_sql_evolution_check_for_dead_fields<br />
    suspect_fields.difference_update(f.aka)<br />
TypeError: iteration over non-sequence
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: derek</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11627</link>
		<pubDate>Wed, 25 Jul 2007 02:40:00 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11627</guid>
					<description>david: that's my goal
rtconner: yes to your second question</description>
		<content:encoded><![CDATA[<p>david: that&#8217;s my goal<br />
rtconner: yes to your second question
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: rtconner</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11625</link>
		<pubDate>Tue, 24 Jul 2007 22:51:50 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11625</guid>
					<description>Or is there any equavalent for this planned for Django root? does this patch work with .97-latest?</description>
		<content:encoded><![CDATA[<p>Or is there any equavalent for this planned for Django root? does this patch work with .97-latest?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Grant</title>
		<link>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11599</link>
		<pubDate>Mon, 23 Jul 2007 18:32:33 +0000</pubDate>
		<guid>http://kered.org/blog/2007-07-19/django-schema-evolution/#comment-11599</guid>
					<description>Is this going to be merged into Django proper?</description>
		<content:encoded><![CDATA[<p>Is this going to be merged into Django proper?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
