Re: Generic views in magic removal

at when I don't pass the info_dict there's still a variable queryset with the string value '1' and with passing it I get the "object_detail() got multiple values for keyword argument 'queryset'" error. Strange Thanks, Arthur --~--~-~--~~~---~--~~ You received

multiple ManyToMany mess

). Am I missing something obvious? Does the fact the the same model has an OneToOneField makes a difference? If it matters... I am running svn with mysqsl 4.1 on os x, python 2.4 Thanks a lot. Arthur --~--~-~--~~~---~--~~ You received this message because you are

Re: Generic views in magic removal

Thanks Max. That's what I tried first. But from the partially updated tutorial in the mr branch docs and the error message "object_detail() got multiple values for keyword argument 'queryset'" when I try that I surmised that the info_dict somehow gets implicitly passed. Where could

Generic views in magic removal

lts import * from models import TodoItem info_dict = { 'queryset': TodoItem.objects.all() } urlpatterns = patterns( 'django.views.generic.list_detail', (r'(\d+)/$', 'object_detail'), ) Any help appreciated. Thanks Arthur --~--~-~--~~~---~--~~ Yo

Re: magic-removal: 'module' object has no attribute ''

> > > > AttributeError: 'module' object has no attribute 'someapp' > > And is there a directory named "myapp" under the directory > "myproject"? Argh, I've got the old directory structure with "apps", but didn't look at the right pla

Re: magic-removal: 'module' object has no attribute ''

go.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'myproject.myapp', ) The error naturally only occurs with the last line. Did I miss something? Thanks again Arthur --~--~-~--~~~---~--~~ You received this mess

magic-removal: 'module' object has no attribute ''

]) AttributeError: 'module' object has no attribute 'someapp' Thanks Arthur --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegro

Re: Django scalability question

The other day I visited Rob Curley in Naples and got a good look at the tremendous work Rob (and the whole ljworld team) have done with school sports databases. Individual stats on a thousand players. My question is, what happens if I try to use Django to do the same thing at the New York Daily

Re: Newspapers

Ellington looks pretty interesting. From my point of view, a lot of folks are sort of following along in the backwash of LJWorld. And of course that was the basic point of my original inquiry. Doesn't seem like Ellington has been widely used elsewhere, though. Wonder how many people here have had

Newspapers

Adrian H. suggested I post a note explaining that I'm very interested in talking to Django developers who have experience with interactive publishing projects. I'm trying to gauge the suitability of Django for a major big-city newspaper site and find some really smart developers who might be

Re: memory usage

low memory consumption is of importance to you, you might consider upgrading. Arthur

OneToOneField extending User: is this the best way?

y if there are typos on this code, I am just trying to provide am example... Any thoughts on this? Thanks a lot, arthur p.s.: I guess after the new admin branch is merged it will be trivial to subclass user but I have an app to deliver sooner than that so...

Re: imagefield, admin, wrong link

Hi Gabor, I am dealing with the same issue here, and I've opened a ticked for this : http://code.djangoproject.com/ticket/1315 It seems that on the admin's template ('file.html'), filefields are susbtituted to "bound_field.original_url" which evaluates to blank even if you use the

Re: Superfluent _id in field name results in SQL error

column name instead of its > own column name. Should've been: > > col_type = db.DATA_TYPES[data_type] if col_type is not None: --> > field_output = [db.db.quote_name(f.column), col_type % f.__dict__] > field_output.append('%sNULL' % (not f.null and 'NOT ' or '')) Thanks for the pointer to the source. That looks better. I still don't understand, why an _id gets attached. Isn't that only for primary keys? And what's that constraint doing there? I've filed a ticket: http://code.djangoproject.com/ticket/1165 Thanks again, Arthur

Superfluent _id in field name results in SQL error

NULL REFERENCES "invoicing_invoices" ("invoice_number"), "id" serial NOT NULL PRIMARY KEY ); Where does this superfluous _id come from? It's not in the model. And if it's automagically added, why isn't it added to the CHECK clause? What's that CHECK clause doing there anyway, it's already in the referenced table? Thanks for any help, Arthur.

<    1   2