Calculating the /jsi18n/ link

script (with gettext defined in it), but going to plain old https://kulleen.org/jsi18n/ does not. So the question is this: how is that stuff in the comments getting miscalculated, and how can I correct that calculation? I've got django with apache2 and mod_wsgi. Thanks! Seemant --~--~-~--~-

Re: Auto-archive lists

Hi Everyone, Thanks really much for all those pointers! Templatetags are exactly what I wound up doing. RossP -- thanks for your blog and example download code -- saved me to see actual working stuff :) Cheers, Seemant --~--~-~--~~~---~--~~ You received

Re: unique_together

, Seemant --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED

Re: unique_together

in it. So, Genesis 1:1 is "not unique" apparently, either. Thanks! Seemant > > Of course yo should zap the DB and make manage.py re-create if from > scratch from the models (so the additional UNIQUE constraint is set) > before testing > this. Yes, rm'd the

Re: unique_together

OK, I've just made a discovery everyone. It works if you have a to_verse. But if to_verse is "None" or NULL or whatever, then it just adds it. So Genesis 1:1-2 will catch uniqueness but Genesis 1:1 will not. Thanks! Seemant --~--~-~--~~~---~--~~ Yo

Re: unique_together

); sqlite> insert into "sermons_scripture" (id, book, chapter, from_verse,to_verse, passage) values (2, "1", 1, 1, 2, "passage"); SQL error: columns book, chapter, from_verse, to_verse are not unique Thanks, Seemant --~--~-~--~~~---~--~

Re: unique_together

quot;); sqlite> insert into "sermons_scripture" (id, book, chapter, from_verse, to_verse, passage) values (1, "1", 1, 1, 2, "passage"); SQL error: PRIMARY KEY must be unique sqlite> Thanks, Seemant --~--~-~--~~~---~--~~ You re

Re: unique_together

Hi RajeshD, I do indeed get an error: SQL error: PRIMARY KEY must be unique --~--~-~--~~~---~--~~ 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@googlegroups.com

Re: unique_together

'), ('70', '3 John'), ('71', 'Jude'), ('72', 'Revelations'), ) The version of sqlite I have here is 3.3.8 Thanks! Seemant PS I have no idea how this SQL INSERT business works at all. --~--~-~--~~~---~--~~ You received this message because

Re: unique_together

to_verse" integer NULL, "passage" varchar(50) NOT NULL, UNIQUE ("book", "chapter", "from_verse", "to_verse") ); Thanks! Seemant --~--~-~--~~~---~--~~ You received this message because you are subscrib

Auto-archive lists

but the template (and adrian's commit message) seem to imply that that list is generated manually. Is there no construct in Django that will auto-gen a link list like that? Thanks! Seemant --~--~-~--~~~---~--~~ You received this message because you are subscribed

ForeignKey field with null = True and blank = True

can never choose one. That is to say, I can choose one, and hit save and when I come back in it's unchosen. Happens every single time. I've attached the services/models.py and sermons/models.py if that helps. Thanks! Seemant --~--~-~--~~~---~--~~ You received

Re: ManyToManyFields are not syncdb'able

Andy, Duh on me :( Thanks for all your help with this -- it works beautifully now. My next challenge is date based generic views, but I'll open a new thread on that for archival's sake. Thanks again! Seemant --~--~-~--~~~---~--~~ You received this message

Re: ManyToManyFields are not syncdb'able

in lookup_inner, line 835 Thanks! Seemant --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscribe from this group,

Re: ManyToManyFields are not syncdb'able

services_service_altar_guild" ( "id" integer NOT NULL PRIMARY KEY, "service_id" integer NOT NULL REFERENCES "services_service" ("id"), "person_id" integer NOT NULL REFERENCES "people_person" (

ManyToManyFields are not syncdb'able

Dear All, I've attached two files: people/models.py and services/models.py. I have two many-to-many relationships defined: one is between people and roles (each person can fill many roles, and each role can be filled by many people); and one is between each activity in the service (banner

Efficient ways to limit_choices_to

per solution is implemented. Thanks for your time! Seemant --~--~-~--~~~---~--~~ 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@googlegroups.com To unsubscri