Re: MySQL BINARY WHERE Clauses

2008-07-21 Thread Malcolm Tredinnick
On Tue, 2008-07-22 at 01:29 -0500, David Cramer wrote: [...] > In summary, this is, in fact, a problem in the Django codebase, and > need's addressed, as it's causing issues for myself, and probably a > number of other people, even if they haven't realized it yet. So let's start off by assuming

Re: MySQL BINARY WHERE Clauses

2008-07-21 Thread David Cramer
Sorry, to be more clear, that is an *exact* match on what is in the database, but using the BINARY form does not return the result. On Tue, Jul 22, 2008 at 1:45 AM, Malcolm Tredinnick < [EMAIL PROTECTED]> wrote: > > > On Tue, 2008-07-22 at 01:29 -0500, David Cramer wrote: > [...] > > In summary,

Re: MySQL BINARY WHERE Clauses

2008-07-21 Thread Mike Scott
David, We know you know the difference, but you should also know how much we love detail. More detail is also needed here. On Tue, Jul 22, 2008 at 6:29 PM, David Cramer <[EMAIL PROTECTED]> wrote: > I don't want to seem harsh Karen, but I understand the differences in the > user lists. This is

Re: MySQL BINARY WHERE Clauses

2008-07-21 Thread David Cramer
I don't want to seem harsh Karen, but I understand the differences in the user lists. This is not an issue with how I'm using Django, it's an issue with what Django's doing. This may be better suited as a ticket, but I'd rather not end up with another trac ticket that emails me daily because it tur

Re: MySQL BINARY WHERE Clauses

2008-07-21 Thread Karen Tracey
On Tue, Jul 22, 2008 at 2:13 AM, David Cramer <[EMAIL PROTECTED]> wrote: > > I was using utf8_general. I'm swapping to utf8_bin to attempt to fix > it, but binary encodings cause problems as well with unique indexes or > something similar (can't remember what my test case was from Curse). > > On J

Re: Last call for 1.0 alpha

2008-07-21 Thread Jeremy Dunck
On Mon, Jul 21, 2008 at 10:49 AM, Marty Alchin <[EMAIL PROTECTED]> wrote: > I certainly hope 1.0 alpha isn't about hitting the > backwards-compatible limit yet, because if it is, #5361 has failed to > make the cut in time. The way I understand it, we still have some time > to introduce mild incomp

Re: django sites subframework confusing

2008-07-21 Thread Malcolm Tredinnick
On Mon, 2008-07-21 at 20:27 -0700, Trent wrote: > Hi all- > > I am having a very hard time tracking down some detailed documentation > on the sites subframework. I have read the django book and gone > through the tutorial. I've also read the Sites documentation page. I > find the documentatio

Re: Last call for 1.0 alpha

2008-07-21 Thread Karen Tracey
On Mon, Jul 21, 2008 at 12:57 PM, Chris Hasenpflug < [EMAIL PROTECTED]> wrote: > > I've opened #7867 for regressiontests.model_inheritance_regress > failures against MySQL. I've marked it 1.0 beta for now, but > depending on requirements of the test suite passing before tagging a > release. it ma

django sites subframework confusing

2008-07-21 Thread Trent
Hi all- I am having a very hard time tracking down some detailed documentation on the sites subframework. I have read the django book and gone through the tutorial. I've also read the Sites documentation page. I find the documentations page provides the most details to the uses of the subframe

Re: SCRIPT_NAME/PATH_INFO, etc, changes

2008-07-21 Thread Jacob Kaplan-Moss
On Mon, Jul 21, 2008 at 7:54 AM, Richard Davies <[EMAIL PROTECTED]> wrote: > The question is how Django should handle cases when PATH_INFO is not > set in the environment with which WSGI is called. The options are: >From the WSGI spec: """ environ Variables [...] The following variables **must*

Re: Installing alpha over 96.x?

2008-07-21 Thread Karen Tracey
On Mon, Jul 21, 2008 at 2:28 PM, Ramiro Morales <[EMAIL PROTECTED]> wrote: > > On Mon, Jul 21, 2008 at 3:17 PM, Karen Tracey <[EMAIL PROTECTED]> wrote: > > I just tried installing current svn (via setup.py) on a machine where I > had > > previously installed 0.96.2. Install works but I notice tha

Re: Last call for 1.0 alpha

2008-07-21 Thread Tom Tobin
On Mon, Jul 21, 2008 at 10:18 AM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > If there's anything that absolutely *MUST* be in 1.0 alpha, speak up > now. Please keep in mind that the alpha release is intended only for > the "must-have" features, which are now all in. This means that the > only

Re: Last call for 1.0 alpha

2008-07-21 Thread Chris Hasenpflug
I've opened #7867 for regressiontests.model_inheritance_regress failures against MySQL. I've marked it 1.0 beta for now, but depending on requirements of the test suite passing before tagging a release. it may need to reassigned. It looks like a mix-up of True/1 and False/0, but I havent really

Re: Table Row count: Limiting factor

2008-07-21 Thread Malcolm Tredinnick
On Mon, 2008-07-21 at 08:13 -0700, madhav wrote: > Hello guys, I am just confused with a fundamental db problem. I have > table which has got 48 lakh rows(each row has got 8 fields, all > INDEXED) and I just need to fetch 500 rows from it. Would that take > more time than extracting the same numb

Re: Installing alpha over 96.x?

2008-07-21 Thread Ramiro Morales
On Mon, Jul 21, 2008 at 3:17 PM, Karen Tracey <[EMAIL PROTECTED]> wrote: > I just tried installing current svn (via setup.py) on a machine where I had > previously installed 0.96.2. Install works but I notice that there are > files (contrib/admin/urls.py, contrib/admin/utils.py are two I knew to

Re: Installing alpha over 96.x?

2008-07-21 Thread Brian Rosner
On Jul 21, 2008, at 12:17 PM, Karen Tracey wrote: > I just tried installing current svn (via setup.py) on a machine > where I had previously installed 0.96.2. Install works but I notice > that there are files (contrib/admin/urls.py, contrib/admin/utils.py > are two I knew to check for) th

Installing alpha over 96.x?

2008-07-21 Thread Karen Tracey
I just tried installing current svn (via setup.py) on a machine where I had previously installed 0.96.2. Install works but I notice that there are files (contrib/admin/urls.py, contrib/admin/utils.py are two I knew to check for) that used to exist in the old version but have been deleted in curren

Re: Last call for 1.0 alpha

2008-07-21 Thread Chris Hasenpflug
On Jul 21, 12:04 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > Are you saying these JUST started failing for MySQL?  This True/1 False/0 > issue has been known for a while (http://code.djangoproject.com/ticket/7190 > ). Wow...I'm on a roll today, lol. Somehow I didn't manage to find that one i

Re: Last call for 1.0 alpha

2008-07-21 Thread Marty Alchin
On Mon, Jul 21, 2008 at 11:37 AM, Tom Tobin <[EMAIL PROTECTED]> wrote: > Gah, I really haven't had time to do the > move-code-out-of-__init__-modules dance. I'm fairly certain that > it'll be completely backwards compatible (via re-importing back into > __init__), though, so I'm not too worried;

Re: Last call for 1.0 alpha

2008-07-21 Thread Jacob Kaplan-Moss
On Mon, Jul 21, 2008 at 8:48 AM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote: > I'm not at OSCON, but I can take care of #7864 (docs renaming), as I've > got a patch already in the works. Cool - go ahead and check that in; I'll give it a quick skim-over but doc fixes are easily done a bit after if

Re: Last call for 1.0 alpha

2008-07-21 Thread Jacob Kaplan-Moss
On Mon, Jul 21, 2008 at 8:48 AM, Karen Tracey <[EMAIL PROTECTED]> wrote: > I think it would be good if #7414 was fixed for alpha. Good call. I'm on 10.5 here so I can test it and get it done. Jacob --~--~-~--~~~---~--~~ You received this message because you are s

Re: Last call for 1.0 alpha

2008-07-21 Thread Gary Wilson Jr.
Jacob Kaplan-Moss wrote: > [If you happen to be at OSCON I'll be working on 1.0 alpha on the > lower floor over by the Starbucks if you wanna come over and help > out.] I'm not at OSCON, but I can take care of #7864 (docs renaming), as I've got a patch already in the works. Gary --~--~

Re: Last call for 1.0 alpha

2008-07-21 Thread Karen Tracey
On Mon, Jul 21, 2008 at 11:18 AM, Jacob Kaplan-Moss < [EMAIL PROTECTED]> wrote: > If there's anything that absolutely *MUST* be in 1.0 alpha, speak up > now. Please keep in mind that the alpha release is intended only for > the "must-have" features, which are now all in. This means that the > only

Last call for 1.0 alpha

2008-07-21 Thread Jacob Kaplan-Moss
Hi folks -- Well, with #285 fixed (thanks, Malcolm!) we're looking pretty good to release 1.0 alpha later today. Time-wise I think the plan is to do the release late this afternoon (CST), but that's really up to James. There's still a few tickets open in the 1.0 alpha milestone (http://code.djan

Admin validation

2008-07-21 Thread Honza Král
Hi, is there any reason at all for a formset used in edit inline to be subclass of BaseModelFormSet aside from ease of use? We currently have a few instances where we do not want the individual forms to correspond 1to1 to model instances and this checks does not make any sense in that case. Could

Re: SCRIPT_NAME/PATH_INFO, etc, changes

2008-07-21 Thread Richard Davies
First of all, thank you very much to Malcolm for fixing this - clearly a massive step forwards towards 1.0! I've subsequently had a discussion on the #3414 ticket tracker, which I'm now moving to django-developers before it becomes too lengthy, as per the "How to contribute". The question is ho

Re: Is URL template tag's syntax going to change?

2008-07-21 Thread Nicola Larosa (tekNico)
Johannes Dollinger wrote: > Of course that's subjective, everything is. You're in the wrong line of work, man... ;-) -- Nicola Larosa - http://www.tekNico.net/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Djang

Re: #7611 contrib.auth PasswordResetTest requires specific templates for tests to pass

2008-07-21 Thread Russell Keith-Magee
On Sat, Jul 19, 2008 at 1:58 PM, Jason Yan <[EMAIL PROTECTED]> wrote: > > Re: http://code.djangoproject.com/ticket/7611 > > The current situation is that if you create a new Django project and > run the unit tests, the contrib.auth baisc tests fail due to missing > templates. These templates are

Re: Problems with concurrent DB access and get_or_create()

2008-07-21 Thread Ben Godfrey
Hi, I'm using rev 7713 (I need to port to the new upload handling before I can get back to trunk). The code that actually adds to the table: def do_update(self, event): if event.countable: matrix, new = self.get_or_create(date=event.time.date(), memb

Re: #7611 contrib.auth PasswordResetTest requires specific templates for tests to pass

2008-07-21 Thread Jason Yan
> However, if the user is _not_ using the views (e.g., they're using the > auth.User model, but providing their own login views), there is an > argument to be made for skipping the tests. Is it safe to say that if we try to reverse('django.contrib.auth.views.password_reset'), we should not run th

SCRIPT_NAME/PATH_INFO, etc, changes

2008-07-21 Thread Malcolm Tredinnick
In [8015] I finally landed the patch to fix a number of issue with URL parsing that we've been talking about. It explicitly fixes #285, #1516 and #3414, but possibly others as well, and is based on a patch that John Melesky wrote at a sprint last year (although I forgot to thank him in the commit

Re: Translation corrections

2008-07-21 Thread diogobaeder
Thanks a lot, guys! I'm looking forward to make my move into helping Django to evolve! :-) See ya! Diogo On Jul 21, 3:26 am, "Andrews Medina" <[EMAIL PROTECTED]> wrote: > On Mon, Jul 21, 2008 at 12:45 AM, diogobaeder <[EMAIL PROTECTED]> wrote: > > > Hi! > > Hi, > > I'm Brazilian too. > > > >

Re: Is URL template tag's syntax going to change?

2008-07-21 Thread Ivan Sagalaev
Johannes Dollinger wrote: > Afaics the only other tag that would accept an arbitrary unquoted > literal is {% ssi %}. > Are there more? Actually when I've first implemented {% url %} I looked for formatting parameters at {% cycle %}. Which back then had only one syntax: {% cycle val1,val

Re: Is URL template tag's syntax going to change?

2008-07-21 Thread Julien Phalip
I'm also +1 for the change (and in fact, for any change that we would regret not having done after 1.0 goes live). To back this up, the above note has been hanging in the documentation for several months (more than 8, as far as I can track back), so people could not say that they weren't warned.