On 5/9/06, pbx <[EMAIL PROTECTED]> wrote: > Here's another way to look at it, given that we are still at 0.91+: > Besides inertia, what are the arguments in favor of the system Django > currently uses? The only person I've seen address this is Jacob, who > correctly noted in the ticket comments that some beginners would find > the separate settings easier to understand.
Honestly, I think the DSN way of doing things is much more common in the "enterprise" world, and the separate DB name/user/pass settings are more common elsewhere. No matter which one you go with, you're going to have people saying "well I've always done it *that* way". Also, no matter which one is being used, it's trivial to parse it into the other in the settings file; going from DSN to separate settings is a matter of splitting the DSN string, and going from separate settings to a DSN is a matter of concatenating the individual bits. Which means that the one Django actually uses should be the one that's A) simplest and B) likely to be familiar to the broadest spectrum of users of the framework. Based on those criteria, I'd say separate settings are the way to go. > Imagine if the current situation were reversed -- Django supported DSNs > only, and a ticket were filed to abandon them and change to the > DATABASE_* style. How would that ticket fare? Probably better than this one is faring. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
