On Sun, Mar 1, 2009 at 7:41 AM, Alex Myodov <[email protected]> wrote:
> > Well, according to "If there's some really strong use-case that's been > overlooked here, it can be brought up in a thread on django-dev", I > think I need to explain the feature a bit better. > > Why we may ever need to have autofields being non-primary-keys? > To be able to use several autofields in a single model. > I don't have time to read this right now because I am on my out the door, but another thing beyond a use case needed to get this reconsidered is a way to actually make it work. The initial description contended that all that was needed was removal of two asserts in the current code. That is not true, at least for a few of the backends. MySQL, if I recall correctly, flat-out will not support this at all. I dislike the idea of adding any (more) behavior that works differently across backends, so it would be nice to hear that I'm wrong on that, but I haven't heard it yet. PostgresSQL and Oralce didn't work right out of the box either, though there may be other code added that could make them work. But someone interested in making this work will need to do the legwork here to articulate what exactly would be needed to make this work across all supported backends, or at least which ones can support it and how. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
