#4001 - newforms commit=false and m2m data loss

Hi all, I've been looking at ticket #4001, and the problem with form_for_model and form_for_instance losing m2m data if you use commit=False. The comment in the code has a FIXME, with a comment that we should raise an exception in this case. The ticket has a patch, contributed by SmileyChris,

Re: edit_inline for a reflexive m2m_intermediary

On 7/20/07, Nicola Larosa <[EMAIL PROTECTED]> wrote: > > Tom Tobin wrote: > > Django-developers isn't a "Help Desk Level 2"; please don't try to use > > it as such. ... > Having followed all the steps in the bug reporting guidelines, I have > now filed ticket #4937: For future reference, you

Re: schema evolution

On 7/20/07, Derek Anderson <[EMAIL PROTECTED]> wrote: > > heh, i read this and was like "there are other backends?!?" ;p > > nope, sqlite/mysql/postgres is all she wrote right now, as that was all > that existed last summer when i did the bulk of the work on this. but > i'll add oracle and

Re: edit_inline for a reflexive m2m_intermediary

On 7/20/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > > Hi, > > actually, I find it a legitimate use of django-developers to report errors > that are probably caused by Django and look weird, especially if the mail > concentrates on the bug description and is, well, developer style (full >

Re: edit_inline for a reflexive m2m_intermediary

On 7/20/07, Nicola Larosa <[EMAIL PROTECTED]> wrote: > > Tom Tobin wrote: > > Django-developers isn't a "Help Desk Level 2"; please don't try to use > > it as such. > > Maybe too much politeness on my part obscured the main point, so let's be > blunt this time: > > there's a bug in Django. (Oh,

Re: schema evolution

heh, i read this and was like "there are other backends?!?" ;p nope, sqlite/mysql/postgres is all she wrote right now, as that was all that existed last summer when i did the bulk of the work on this. but i'll add oracle and mssql, if someone can provide me access to a test db. (well,

Re: edit_inline for a reflexive m2m_intermediary

Hi, actually, I find it a legitimate use of django-developers to report errors that are probably caused by Django and look weird, especially if the mail concentrates on the bug description and is, well, developer style (full context etc.) It often helps to get to the point (or embarrass yourself

Re: schema evolution

Hi all, Derek, nice job! does your solution support all of the db backends or just sqlite/mysql/postgres? (we use a hacked version of dbmigration (http://www.aswmc.com/ dbmigration/) at work - works like a charm.) Thanks, Peter On Jul 20, 11:22 am, Sebastian Macias <[EMAIL PROTECTED]> wrote:

Re: edit_inline for a reflexive m2m_intermediary

Tom Tobin wrote: > Django-developers isn't a "Help Desk Level 2"; please don't try to use > it as such. Maybe too much politeness on my part obscured the main point, so let's be blunt this time: there's a bug in Django. (Oh, the horrors! ;-P ) Or maybe not, whatever. Having followed all the

Re: schema evolution

Thanks for the hard work. I have been looking for this forever. It should definitely be merged to trunk as Django proper. Sebastian Macias On Jul 19, 5:33 pm, Derek Anderson <[EMAIL PROTECTED]> wrote: > Hey all, > > Sorry for the double-post, but I've written up some examples / > documentation:

Re: edit_inline for a reflexive m2m_intermediary

On 7/20/07, Nicola Larosa <[EMAIL PROTECTED]> wrote: > > [Sent this to the users list with no answer, and who knows, maybe it's not > me, but actually a bug instead. :-) I also tried using the newforms-admin > branch, but most URLs are absent or commented out...] [...] > What am I missing?

Re: Ticket #399 (Bigint field object needed) status

+1 to bigint support. I ran into this problem recently when implementing IP geolocation models. I know I'm not the only one that has or will experience these problems (remember when slashdot crashed after 16,777,216 comments?). >From what I understand, the largest hurdle to having large

edit_inline for a reflexive m2m_intermediary

[Sent this to the users list with no answer, and who knows, maybe it's not me, but actually a bug instead. :-) I also tried using the newforms-admin branch, but most URLs are absent or commented out...] I'm following the m2m_intermediary pattern: 9. Many-to-many relationships via an

Re: Unicode and pickles

On Fri, Jul 20, Gábor Farkas wrote: > > Michael Radziej wrote: > > Hi, > > > > I think I've hit a show stopper. > > > > I'm still porting my application to Unicode ... well, before the > > unicode > > changes it was possible to use a TextField for pickles, like > > contrib.Session > > does

Re: Unicode and pickles

On Fri, Jul 20, Michael Radziej wrote: > > Hi, > > I think I've hit a show stopper. > > I'm still porting my application to Unicode ... well, before the > unicode > changes it was possible to use a TextField for pickles, like > contrib.Session > does (Session.session_data). > > But pickling

Re: Unicode and pickles

Michael Radziej wrote: > Hi, > > I think I've hit a show stopper. > > I'm still porting my application to Unicode ... well, before the > unicode > changes it was possible to use a TextField for pickles, like > contrib.Session > does (Session.session_data). > > But pickling gives a bytestring,

Unicode and pickles

Hi, I think I've hit a show stopper. I'm still porting my application to Unicode ... well, before the unicode changes it was possible to use a TextField for pickles, like contrib.Session does (Session.session_data). But pickling gives a bytestring, and this isn't necessarily valid UTF-8.

Re: Django 1.0?

Yeah, but you just know that as soon as the theories get interesting, the network will pull the plug On 7/20/07, oggie rob <[EMAIL PROTECTED]> wrote: > > > If you have the time, Mario, you can always create a "django 1.0 > release theories" website :) > Then all you have to do is come up with