Re: Constraints and MySQL

On 3/1/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > > Andy Dustman: > > Here's another possible solution/workaround: MySQL supports an IGNORE > > keyword on INSERT statements, which causes errors to be treated as > > warnings. > > > > http://dev.mysql.com/doc/refman/5.0/en/insert.html > > > >

Re: Upcoming changes to the Django admin

On 3/3/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > Jacob Kaplan-Moss wrote: > > Edit-inline is also going to be moved out into the admin declaration, > > Edit-inline was also useful outside of the admin, in manipulators. Are > there any plans to have newforms handling this or this will become

Re: Upcoming changes to the Django admin

Jacob Kaplan-Moss wrote: > Edit-inline is also going to be moved out into the admin declaration, Edit-inline was also useful outside of the admin, in manipulators. Are there any plans to have newforms handling this or this will become a purely admin functionality? --~--~-~--~~-

Re: ABSOLUTE_URL_OVERRIDES issue

On 2/28/07, Nicolas Steinmetz <[EMAIL PROTECTED]> wrote: > I added the following piece of "code" in settings.py (is it the right > place ?) but it does not work (it looks it's not take into account with > django svn 4643). > > ABSOLUTE_URL_OVERRIDES = { > 'cab.Language' : lambda o: "/snippets/

Re: Bug in Admin's Change Password form

And almost immediately marked as a duplicate. :-) Guess I should read through all of my mail before acting on any of it. On Sat, 2007-03-03 at 08:52 -0500, Todd O'Bryan wrote: > Done. #3645 > > On Fri, 2007-03-02 at 16:38 -0800, Simon G. wrote: > > Hi Todd, > > > > Can you drop by code.djangop

Re: Bug in Admin's Change Password form

Done. #3645 On Fri, 2007-03-02 at 16:38 -0800, Simon G. wrote: > Hi Todd, > > Can you drop by code.djangoproject.com and create a ticket for this, > so we don't lose trac (sorry) of it. > > Thanks :) > Simon G. > > > > --~--~-~--~~~---~--~~ You received this

Re: select_related() changes

The main problem with depth=1 seems to be, that the query generator still spans over too many tables (watching the mysql.log i can see tables fully joined that definitvly do not belong to level 1). Thus the returned data set will surely confuse django. Looking at django/db/models/query.py reveals

Re: multiple-db-support branch

Done, it's http://code.djangoproject.com/ticket/3644 A patch is included. Ciao, Marc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develope

Re: Constraints and MySQL

On Mar 2, 2007, at 12:50, mario__ wrote: > > On Feb 27, 8:31 pm, "Marc Fargas Esteve" <[EMAIL PROTECTED]> wrote: >> -1 on option 1, and +1 in option 2. We should not remove >> functionality because MySQL can't deal with that, simply document >> "this won't work with mysql" :) >> > > +1 Great

Re: Session Class field question

Thanks Nebojša for your answer Actually, I was asking for development purposes, and as I see, the values which are asked for should not be used or edited by a Django user. If I´m still wrong, I´ll post in the Django users Forum. On Mar 3, 2:15 am, Nebojša Đorđević <[EMAIL PROTECTED]> wrote:

>< Beautify yourself >< - Fair Color and Skin Care

*Beauty Tips for You* *Beautify yourself* ** *[image: Beauty Tips] * http://www.100stuff.com/beauty/beauty_tips/ ** *Skin Care Tips* *Weight Loss* *Smooth Skin* *Fair Color* ** ** *Beauty Tips for you * --~--