<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>Django developers Google Group</title>
  <link>http://groups.google.com/group/django-developers</link>
  <description>Discussion group for Django developers. This group is used for discussion of developing Django itself, not user questions; Please use django-users for issues regarding using the framework, questions for the Django user community outreach, etc.</description>
  <language>en</language>
  <item>
  <title>Re: Problem with history view in admin page</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/2255d614227b65f2?show_docid=2255d614227b65f2</link>
  <description>
  On Tue, Nov 24, 2009 at 7:09 PM, Russell Keith-Magee &amp;lt;freakboy3...@gmail.com &lt;br&gt; &lt;p&gt;Also I believe there&#39;s at least one other place in Django that does similar &lt;br&gt; -- the object_pk in the base contrib.comments model is also a TextField. I &lt;br&gt; suspect any DB backend that has trouble with the admin history view is also
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/2255d614227b65f2?show_docid=2255d614227b65f2</guid>
  <author>
  kmtra...@gmail.com
  (Karen Tracey)
  </author>
  <pubDate>Wed, 25 Nov 2009 00:28:40 UT
</pubDate>
  </item>
  <item>
  <title>Re: Problem with history view in admin page</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/95c6accec63ec0ab?show_docid=95c6accec63ec0ab</link>
  <description>
  Your comment about foolishness is definitely correct :-) As for the &lt;br&gt; CharField point - following this logic, we could define object_id as &lt;br&gt; a CharField(max_length=N), for some large N. However, in the general &lt;br&gt; case, we can&#39;t specify an N that is greater than all N&#39;s that &lt;br&gt; end-users might use. Therefore, we use a TextField, which is unbound.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/95c6accec63ec0ab?show_docid=95c6accec63ec0ab</guid>
  <author>
  freakboy3...@gmail.com
  (Russell Keith-Magee)
  </author>
  <pubDate>Wed, 25 Nov 2009 00:09:47 UT
</pubDate>
  </item>
  <item>
  <title>Re: Why not datetime.utcnow() in auto_now/auto_now_add</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/4ca560ef33c88bf3/f475e168bcda7767?show_docid=f475e168bcda7767</link>
  <description>
  Why would it be? A datetime field isn&#39;t necessarily stored in UTC. It &lt;br&gt; uses datetime.now() because that will return the same time as &lt;br&gt; settings.TIME_ZONE. &lt;br&gt; &lt;p&gt;On top of that, making this change would be a *huge* backwards &lt;br&gt; incompatibility, as any existing uses of auto_now etc would break. &lt;br&gt; &lt;p&gt;Time zone handling is definitely something that Django could handle
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/4ca560ef33c88bf3/f475e168bcda7767?show_docid=f475e168bcda7767</guid>
  <author>
  freakboy3...@gmail.com
  (Russell Keith-Magee)
  </author>
  <pubDate>Tue, 24 Nov 2009 23:36:41 UT
</pubDate>
  </item>
  <item>
  <title>Re: Oracle/GIS Testers Needed</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/149d7c4aabbc034f/deaa453877019c23?show_docid=deaa453877019c23</link>
  <description>
  Initial extent errors happens because datafile allocated for temporary &lt;br&gt; tablespace is full. It&#39;s hardcoded in &lt;br&gt; django/db/backends/oracle/crea tion.py:L159,L163 (in trunk) to be 100M(bytes) &lt;br&gt; which apparently is not enough anymore. Too bad that it&#39;s so late that I &lt;br&gt; don&#39;t have time to test how much space tests actually needs now but it&#39;s
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/149d7c4aabbc034f/deaa453877019c23?show_docid=deaa453877019c23</guid>
  <author>
  rede...@gmail.com
  (redetin)
  </author>
  <pubDate>Tue, 24 Nov 2009 22:09:37 UT
</pubDate>
  </item>
  <item>
  <title>Re: Problem with history view in admin page</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/385d0cef2a3e8182?show_docid=385d0cef2a3e8182</link>
  <description>
  On Mon, Nov 23, 2009 at 11:00 PM, Russell Keith-Magee &lt;br&gt; &lt;p&gt;The decision is based on the field type, not on the individual field. &lt;br&gt; If it were possible within the Oracle backend to override this &lt;br&gt; particular field to VARCHAR2, we would happily do it. But TextFields &lt;br&gt; in general need to be LOBs. &lt;br&gt; &lt;p&gt;Due to the hackish way the Oracle backend implements lookups on LOBs,
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/385d0cef2a3e8182?show_docid=385d0cef2a3e8182</guid>
  <author>
  ian.g.ke...@gmail.com
  (Ian Kelly)
  </author>
  <pubDate>Tue, 24 Nov 2009 17:25:32 UT
</pubDate>
  </item>
  <item>
  <title>Why not datetime.utcnow() in auto_now/auto_now_add</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/4ca560ef33c88bf3/352b0ca3b3197e51?show_docid=352b0ca3b3197e51</link>
  <description>
  DateTimeField &amp;quot;auto_now&amp;quot; and &amp;quot;auto_now_add&amp;quot; used datetime.now(). But &lt;br&gt; why this? IMHO it&#39;s better to use datetime.utcnow(), isn&#39;t it? &lt;br&gt; &lt;p&gt;Mfg. &lt;br&gt; &lt;p&gt;Jens Diemer
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/4ca560ef33c88bf3/352b0ca3b3197e51?show_docid=352b0ca3b3197e51</guid>
  <author>
  google.gro...@jensdiemer.de
  (jedie)
  </author>
  <pubDate>Tue, 24 Nov 2009 16:10:52 UT
</pubDate>
  </item>
  <item>
  <title>django-firebird projects news</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/c78854cc9a7133ac/be12534e9228eba4?show_docid=be12534e9228eba4</link>
  <description>
  Hello everyone, I want to make a summary of the changes implemented in &lt;br&gt; recent times about the project django-firebird: &lt;br&gt; &lt;p&gt;&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://code.google.com/p/django-firebird/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;p&gt;&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://tech.groups.yahoo.com/group/firebird-python/message/254&quot;&gt;[link]&lt;/a&gt;
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/c78854cc9a7133ac/be12534e9228eba4?show_docid=be12534e9228eba4</guid>
  <author>
  map...@gmail.com
  (mariuz)
  </author>
  <pubDate>Tue, 24 Nov 2009 09:37:07 UT
</pubDate>
  </item>
  <item>
  <title>Re: Problem with history view in admin page</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/5162efc248cc0c81?show_docid=5162efc248cc0c81</link>
  <description>
  Well, Django doesn&#39;t make the decision to use CLOB - that&#39;s in the &lt;br&gt; hands of your backend. In the same circumstances, SQLite and Postgres &lt;br&gt; use &#39;text&#39;. MySQL uses &#39;longtext&#39;. Oracle uses &#39;NCLOB&#39; &lt;br&gt; &lt;p&gt;In theory, the contents of the object_id field could be anything - &lt;br&gt; including a string of arbitrary length (i.e., a TextField). However,
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/5162efc248cc0c81?show_docid=5162efc248cc0c81</guid>
  <author>
  freakboy3...@gmail.com
  (Russell Keith-Magee)
  </author>
  <pubDate>Tue, 24 Nov 2009 06:00:50 UT
</pubDate>
  </item>
  <item>
  <title>Re: Problem with history view in admin page</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/5bec1e1f3dff629a?show_docid=5bec1e1f3dff629a</link>
  <description>
  What is stored in this field is a string-serialized representation of &lt;br&gt; the &lt;br&gt; primary key value. &lt;br&gt; &amp;lt;&amp;lt; &lt;br&gt; &lt;p&gt;I agree that INTEGER is not the right choice, but then so too is CLOB. &lt;br&gt; How long is this string-serialized representation going to be? greater &lt;br&gt; than 4000 characters ? Varchar(X) where X is &amp;gt; 4000 or something is
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/f91749b81465ce04/5bec1e1f3dff629a?show_docid=5bec1e1f3dff629a</guid>
  <author>
  mario.bri...@in.ibm.com
  (Mario Briggs)
  </author>
  <pubDate>Tue, 24 Nov 2009 05:07:35 UT
</pubDate>
  </item>
  <item>
  <title>Re: Design decision on FileField removing abandoned files?</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/54baac1d825877ad/4e33aa648bd77b61?show_docid=4e33aa648bd77b61</link>
  <description>
  I&#39;m with you, if not on 100% of what you said, at least 95% of it :) &lt;br&gt; &lt;p&gt;I just foresee that if there is heavy hesitation on even deleting &lt;br&gt; files, deleting directories might be too liberal a feature for the &lt;br&gt; kind of position that the framework takes. I don&#39;t doubt that &lt;br&gt; directory deletion has its use, and that it&#39;s safe when used
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/54baac1d825877ad/4e33aa648bd77b61?show_docid=4e33aa648bd77b61</guid>
  <author>
  tonightslasts...@gmail.com
  (Tim)
  </author>
  <pubDate>Tue, 24 Nov 2009 05:05:52 UT
</pubDate>
  </item>
  <item>
  <title>Re: Design decision on FileField removing abandoned files?</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/54baac1d825877ad/1c861c947c4c7ed7?show_docid=1c861c947c4c7ed7</link>
  <description>
  Hey, it&#39;s not goofy. It&#39;s handy ;) I also took _great_ care when &lt;br&gt; writing the code for directory deletion and it&#39;s happily deleting &lt;br&gt; directories on our production server since a year or so. And it&#39;s of &lt;br&gt; course off by default. That said, if throwing directory deleting out &lt;br&gt; is the thing that&#39;s required to get the patch in, I won&#39;t object ;)
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/54baac1d825877ad/1c861c947c4c7ed7?show_docid=1c861c947c4c7ed7</guid>
  <author>
  jonaspf...@gmx.de
  (Jonas Pfeil)
  </author>
  <pubDate>Tue, 24 Nov 2009 04:41:31 UT
</pubDate>
  </item>
  <item>
  <title>Re: Scaffolding</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/7a524708ecfb6f68/e840facaf59761a4?show_docid=e840facaf59761a4</link>
  <description>
  Hi, &lt;br&gt; I&#39;m working a lot on Model Driven Software Development in the SIDE-Labs &lt;br&gt; project and your approach definitely has a lot of interests for me. We &lt;br&gt; currently chose to work on Alfresco as a framework but we are looking &lt;br&gt; after technological alternatives. &lt;br&gt; &lt;p&gt;Have you been a little further in your thinking?
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/7a524708ecfb6f68/e840facaf59761a4?show_docid=e840facaf59761a4</guid>
  <author>
  j...@bluexml.com
  (Jean-Christophe Kermagoret)
  </author>
  <pubDate>Tue, 24 Nov 2009 03:46:31 UT
</pubDate>
  </item>
  <item>
  <title>Feedback on ticket 7777</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/0deb3047be9de21f/46dc7959efb53ffa?show_docid=46dc7959efb53ffa</link>
  <description>
  Hi, &lt;br&gt; &lt;p&gt;Can I please get some feedback on this ticket? I am hoping that we &lt;br&gt; can get this in soon. &lt;br&gt; &lt;p&gt;&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://code.djangoproject.com/ticket/7777&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;p&gt;Thanks, &lt;br&gt; Farhan
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/0deb3047be9de21f/46dc7959efb53ffa?show_docid=46dc7959efb53ffa</guid>
  <author>
  fah...@gmail.com
  (thebitguru)
  </author>
  <pubDate>Tue, 24 Nov 2009 00:38:48 UT
</pubDate>
  </item>
  <item>
  <title>Re: Public method for getting model field names in order of definition</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/44cd834438cfda77/281fc4a8c95c7b4a?show_docid=281fc4a8c95c7b4a</link>
  <description>
  Another try, view.py: &lt;br&gt; &lt;p&gt;from django.forms.models import model_to_dict &lt;br&gt; &lt;p&gt;def view(request): &lt;br&gt; data = Foo.objects.all()[0] &lt;br&gt; print data.start &lt;br&gt; form = Example(data=model_to_dict(dat a)) &lt;br&gt; return render_to_response(&#39;t.html&#39;, {&#39;form&#39;: form}) &lt;br&gt; &lt;p&gt;Where Example is a ModelForm for model Foo.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/44cd834438cfda77/281fc4a8c95c7b4a?show_docid=281fc4a8c95c7b4a</guid>
  <author>
  akaar...@cc.hut.fi
  (Anssi Kaariainen)
  </author>
  <pubDate>Mon, 23 Nov 2009 18:37:34 UT
</pubDate>
  </item>
  <item>
  <title>Re: Public method for getting model field names in order of definition</title>
  <link>http://groups.google.com/group/django-developers/browse_frm/thread/44cd834438cfda77/5f7f9cf55c073c41?show_docid=5f7f9cf55c073c41</link>
  <description>
  Thanks for the example, but that&#39;s not a ModelForm. &lt;br&gt; &lt;p&gt;Richard
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/django-developers/browse_frm/thread/44cd834438cfda77/5f7f9cf55c073c41?show_docid=5f7f9cf55c073c41</guid>
  <author>
  rlaa...@wiktel.com
  (Richard Laager)
  </author>
  <pubDate>Mon, 23 Nov 2009 17:03:38 UT
</pubDate>
  </item>
  </channel>
</rss>
