Comments for Dashdrum

Comment on Upgrading Django – 1.0 to 1.3 by Dan

Dan — Wed, 07 Mar 2012 00:49:30 +0000

Good luck indeed! Moving from 0.96 to 1.0 will likely be the toughest part.

Comment on Upgrading Django – 1.0 to 1.3 by Erseyg Lacryst

Erseyg Lacryst — Tue, 06 Mar 2012 23:51:41 +0000

1.0 to 1.3 sounds bad. I have to do 0.96 to 1.3 this month. In an absolutely enormous codebase. Wish me luck.

Comment on A Better Way – Don’t! by Using form.save(commit=False) in a Class Based View | Dashdrum

Using form.save(commit=False) in a Class Based View | Dashdrum — Sun, 29 Jan 2012 14:46:56 +0000

[...] UPDATE: I found a better way to do this. See this post. [...]

Comment on Using form.save(commit=False) in a Class Based View by A Better Way – Don’t! | Dashdrum

A Better Way – Don’t! | Dashdrum — Sun, 29 Jan 2012 14:44:52 +0000

[...] an earlier post, I talked about using form.save(commit=False) in a class based view, and I showed a way to do it. [...]

Comment on Class Based Views: CreateView Example by Dan

Dan — Mon, 02 Jan 2012 15:47:17 +0000

Guruprasad, reverse works pretty much the same way as always. The key is to use the as_view() method of the class based view in the URL declaration:

url(r’^create_type/$’,TypeCreateView.as_view(),name=’create_type’),

Then, you can reverse it as usual:

{% url create_type %}
or
reverse(‘create_type’)

Comment on Class Based Views: CreateView Example by Guruprasad

Guruprasad — Fri, 30 Dec 2011 04:53:01 +0000

What I can’t understand here is that, once you have used a class-based generic view, how would reverse(‘create_type’) work? If you leave that view intact it will work. How do I do a reverse if I don’t have a function-based view?

Comment on Class Based Views – DeleteView Example by Class Based Views – UpdateView Example | Dashdrum

Class Based Views – UpdateView Example | Dashdrum — Tue, 15 Nov 2011 18:41:12 +0000

[...] Post navigation ← Previous [...]

Comment on Reporting in Django by Derek

Derek — Sat, 12 Nov 2011 13:38:50 +0000

Any updates on progress with Geraldo – I am in the same situation now and was hoping to benefit from your experiences!

Comment on Eclipse SQL Explorer by My Eclipse Setup for Django | Dashdrum

My Eclipse Setup for Django | Dashdrum — Sat, 01 Oct 2011 13:50:50 +0000

[...] I have also used Eclipse SQL Explorer for database access. It is a bit of a fight to get the proper drivers and configuration all figured out, but worth it to have DB commands within the Eclipse environment here. Read more about SQL Explorer in this earlier post. [...]

Comment on Class-Based Views – Am I Doing It Right? by jaymz

jaymz — Mon, 15 Aug 2011 14:06:20 +0000

“self isnt available” → that doesn’t work at that point because self is a re fence to an *instance* of the class being created. at that stage of your class you’ve not actually created an instance of it yet so “self” is non-existent.

since request is only passed through to methods for the class view the way you set it within the method is correct in terms of the self.request session line.

if you’re looking to provide that variable across your views why not move it into a context processor and pass it into your TEMPLATE_CONTEXT_PROCESSORS tuple in settings?