Hi,
I've been testing out the schema-evolution branch again and hit the
same issue I was having before where it was trying to evolve a model
that hadn't changed. Here are my minimal test case models for this
issue:
from django.db import models
class FooType(models.Model):
name = models.Char
On 11/1/06, John Hwang <[EMAIL PROTECTED]> wrote:
> mysql complains of empty IN() when manytomany field is being saved as
> blank/empty
This looks to be a variation on ticket #2473. It's a known problem,
which I believe Malcolm is working on with his refactor of the query
code.
Yours,
Russ Mage
Regarding the, apparent, less than optimal participation, I think it
might help to dedicate a section on the Django homepage to development
in general or these branches in particular. It's a bit difficult to
find out what needs to be done, it is only posted on this google
discussion group, and aft
I would like to report a bug.
Here is my information: [EMAIL PROTECTED]
the following is the description of the ticket:
Title:
mysql complains of empty IN() when manytomany field is being saved as
blank/empty
Description:
Django complains when I try to create a concert with an edit_inlined
p
I've reported at least a few times on django-dev and django-users that
I've had a lot of success with row-level-permissions. I found some
bugs early on, but Chris Long squashed them all for me. I'm currently
running a production site with that branch.
My requirements of it are pretty minimal, but
I think it would be a good idea to have a bug-squash/testing day on IRC
for certain branches. Maybe the developers of those branches let
someone (?) know they'd like some testing. A day is picked and that's
the testing day. Try to raise awareness on the mailing lists and that
IRC will be the pl
Jay Parlar schrieb:
> I think that Tom Tobin ([EMAIL PROTECTED]) was given the job of
> administering the Trac whitelist.
He whitelisted me (hey, thanks!) when I sent him personal mail.
He will need the IPs you use to access Trac. I guess dynamic IPs
would give him headaches ...
Michael
--
Hi,
Ticket 2482 by mccutchen (thanks!) adds a method 'valuelist()' to
QuerySet. It works similar to values(), but generates tuples
instead of dicts.
I use this, and I really appreciate the idea, but there's one
thing I don't like about it. If you pass only one attribute, it
yields single val
Joe wrote:
> It does bring up the general sort of question - is there a mechanism by
> which individuals can get "whitelisted" or otherwise allowed access to
> the wiki to post up code, patches, etc?
I put some thought into this but couldn't figure out a way to make this
feasible. This would almo
On 10/31/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> This comes up every few weeks.
>
I've wikified this response here:
http://code.djangoproject.com/wiki/ActiveBranches
I linked to any branch detail pages I could find, relevant groups
discussions, and added a suggestion to test one of the
I think that Tom Tobin ([EMAIL PROTECTED]) was given the job of
administering the Trac whitelist.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email t
I forgot to mention that I attempted to put this in the Wiki again and
askimet failed me.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develo
Thanks, Joe. I've actually updated it to this:
from django.conf import settings
from django.contrib.auth.views import login
from django.http import HttpResponseRedirect
class RequireLoginMiddleware(object):
"""
Require Login middleware. If enabled, each Django-powered page will
require
Jared's posted it on his site -
http://superjared.com/entry/requiring-login-entire-django-powered-site/
It does bring up the general sort of question - is there a mechanism by
which individuals can get "whitelisted" or otherwise allowed access to
the wiki to post up code, patches, etc?
I really
Hi
Don't like to hassle, but I'm increasingly wondering what the plan is
for the many new features due to be included in django. I think this
entails these branches:
full-history
multiple-db-support
per-object-permissions
schema-evolution
search-api
sqlalchemy
generic-auth (?)
I'd really like t
On 10/31/06 11:18 AM, Joeboy wrote:
> Don't like to hassle, but I'm increasingly wondering what the plan is
> for the many new features due to be included in django. I think this
> entails these branches:
This comes up every few weeks.
We're really still waiting on end-user testing on the SoC br
On 10/27/06, Jared Kuolt <[EMAIL PROTECTED]> wrote:
>
> I'd like to add a Middleware class that I wrote to the Wiki, but I keep
> getting rejected by askimet.
>
> The class requires an authenticated user for every view. This is
> beneficial for any closed project. Does anyone suppose something lik
Could someone please add [EMAIL PROTECTED]to the whitelist, so i can add tickets to trac.thx-- cu
Wolfram
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, se
18 matches
Mail list logo
