Re: auth.User refactor: reboot

On 20/03/2012, at 8:00 AM, Ian Lewis wrote: >> * One very big new feature -- the ability to have multiple User models in >> the same project. >> >> This is the one controversial part of your proposal, from my perspective. In >> every situation I can think of, I can only see it being an annoyi

Re: auth.User refactor: reboot

Hi, On Mon, Mar 19, 2012 at 9:27 PM, Russell Keith-Magee wrote: > On 18/03/2012, at 12:19 PM, Ian Lewis wrote: >> I meant one that was a completely separate concrete base model. The >> current auth forces you to take along with you all the fields on the >> User model. > > In the current setup, th

Re: Looking for some insight into a tiny piece of the django codebase

Hi Tim, On 03/19/2012 05:17 PM, Tim Diggins wrote: > I'm wondering what the lines at the end of django/db/models/ > deletion.py do: > > for model, instances in self.data.iteritems(): > for instance in instances: > setattr(instance, model._meta.pk.attname, None)

Re: Looking for some insight into a tiny piece of the django codebase

On Mon, Mar 19, 2012 at 11:17 PM, Tim Diggins wrote: > Hi - > > I'm wondering what the lines at the end of django/db/models/ > deletion.py do: > >        for model, instances in self.data.iteritems(): >            for instance in instances: >                setattr(instance, model._meta.pk.attname

Looking for some insight into a tiny piece of the django codebase

Hi - I'm wondering what the lines at the end of django/db/models/ deletion.py do: for model, instances in self.data.iteritems(): for instance in instances: setattr(instance, model._meta.pk.attname, None) They're at the end of the delete method from Collector c

Re: authentication by email

I'm not a dev that contribute too many directly to Django Project, but aniway I use Django since 0.96, so here is my 2 cents. While Clay's idea have many cool changes and is a really nice idea that should be evaluated I share more Tom's and Daniel's point. Any Django Developer on World that chan

Re: Improved Error Reporting in Django - GSoC

On 19/03/12 18:12, Sachin Gupta wrote: Hi, My name is Sachin Gupta and I am student of Indian Institute of Technology Roorkee, in my final year of undergraduate course in Computer Science. I have been developing a project entirely based on Django for the last 4 months. Here is the link

Re: Schema Alteration API proposal

On 19/03/12 20:33, Kushagra Sinha wrote: Andrew's thread[1] also mentions - "backends will always be able to generate SQL for operations, but it won't necessarily be runnable (things like index names can only be resolved at runtime, so you'd get code like "DROP INDEX <> ON users;"." [1] https:/

Re: Schema Alteration API proposal

I have been updating the Wiki a bit ( https://code.djangoproject.com/wiki/SchemaEvolutionDesign). If you see the linked page about the design, it's based on a general approval I got from Russell. I haven't finished writing it up, but it has been in the 60's and 70's in Wisconsin in March. Needless

Re: Schema Alteration API proposal

Check the edit dates on that wiki -- most of the content on that page is historical, reflecting discussions that were happening over 3 years ago. There have been many more recent discussions. Sincere apologies. The page says "Last modified 10 days ago". I thought it was pretty recent and didnt che

Improved Error Reporting in Django - GSoC

Hi, My name is Sachin Gupta and I am student of Indian Institute of Technology Roorkee, in my final year of undergraduate course in Computer Science. I have been developing a project entirely based on Django for the last 4 months. Here is the link and it has been

Re: auth.User refactor: reboot

Yes, it's not really a security bug! It's about to build a more secure account system. On Monday, 19 March 2012 19:25:24 UTC+8, Florian Apolloner wrote: > > Hi lepture, > > aside from the fact, that it's not really a security bug we do ask people > not to report security issues public but mail t

Re: Schema Alteration API proposal

On Mar 19, 2:32 pm, Jani Tiainen wrote: > Here I would like to rise my concern - specially being long time Django > and Oracle user.. =) > > First at all everyone can get hands on Oracle Express database, free of > charge standard Django stuff works in it very well. Geodjango doesn't > work with i

Re: [GSoC 2012] Schema Alteration API proposal

19.3.2012 13:15, Andrew Godwin kirjoitti: On 19/03/12 11:08, Jonathan French wrote: On 18 March 2012 23:33, Russell Keith-Magee mailto:russ...@keith-magee.com>> wrote: > 2. An inspection tool that generates the appropriate python code after > inspecting models and current state of database. Th

Re: auth.User refactor: reboot

On 18/03/2012, at 12:19 PM, Ian Lewis wrote: >>> 5. Basic username (or email)/password authentication can be provided. >>> The app has a base user class from which a basic abstract user with >>> username/password is defined. This can implement setting passwords >>> properly and provide forms etc.

Re: auth.User refactor: reboot

Hi lepture, aside from the fact, that it's not really a security bug we do ask people not to report security issues public but mail to security at djangoproject.com. Reporting them in the open does help neither you nor us. And please don't hijack threads like this -- this thread is about a com

Re: [GSoC 2012] Schema Alteration API proposal

On 19/03/12 11:08, Jonathan French wrote: On 18 March 2012 23:33, Russell Keith-Magee mailto:russ...@keith-magee.com>> wrote: > 2. An inspection tool that generates the appropriate python code after >inspecting models and current state of database. The current consensus is

Re: [GSoC 2012] Schema Alteration API proposal

On 18 March 2012 23:33, Russell Keith-Magee wrote: > > 2. An inspection tool that generates the appropriate python code after > >inspecting models and current state of database. > > The current consensus is that this shouldn't be Django's domain -- at > least, not in the first instance. It mi

Re: auth.User refactor: reboot

Hello, Jacob. The current auth module has a very security bug, if the session cookie is stolen by others, you cannot do anything to stop them. You changed your password, but the session is still working. You signed out, the session is still working. You can do nothing, but waiting for the sessi

RE: commit_on_success leaves incorrect PostgreSQL isolation mode?

This issue is handled in ticket #16407 (https://code.djangoproject.com/ticket/16047), but it is unlikely to get fixed in 1.4. Making changes to transaction management code at this late stage of development cycle isn't something I am willing to do. Your analysis of the cause of the problem is co