On Wed, Apr 29, 2009 at 8:24 PM, Simon Willison <si...@simonwillison.net>wrote:
> > On Apr 30, 12:25 am, Alex Gaynor <alex.gay...@gmail.com> wrote: > > My question would be how is using a DSN and letting those be passed > directly > > to using() any advantage over letting someone pass a dict of those > options > > to using(), or a connection object itself. > > No advantage at all - I'm interested in being able to hand a > dynamically constructed connection to using(), and I don't > particularly mind if it's a DSN, a dictionary or a connection object > I've created already. > > My principle arguments for DSNs are the other two - we already use > them for cache backends, and it's what SQLObject and SQLAlchemy do. > > > Well, my argument for keeping the dictionary maps to, we *already* use it for database settings ;). Also, I personally find DSNs hard to read. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
