Entries published on August 29, 2006
So today I got to wade through the joyful experience of cancelling my account with a business which shall remain nameless (unless, of course, they didn’t actually cancel the account — in which case they shall be named and shamed and several other things as well).
The experience was less then pleasant both for me and the poor customer-service rep who had to take my call, so I’d like to suggest some general guidelines on how this could have gone better. If you want me to be a happy customer, even when I’m ending my relationship with you, you’ll pay attention to these:
- If I can sign up for your service over the web, I should be able to cancel it over the web. Period. No gimmicks, no “please call between the hours of 8:30 AM and 5:30 PM Pacific Standard Time”. I should be able to close my account as easily …
The best of all worlds
Every once in a while, someone will complain on the Django users mailing list that they feel our ORM doesn’t offer all the features they need, and it’s true that there are a few exotic and/or advanced things that it can’t handle. Usually the standard people compare to is SQLAlchemy which can be, unfortunately, extremely complex to learn and use. A related — and inaccurate — complaint is that it’s possible to use Django with SQLAlchemy, but that you’d lose the admin app (you wouldn’t; using the admin while your own views rely on another ORM, or even another framework entirely, is actually pretty easy).
Either way, both complaints are about to go out the window: a new Django branch, created literally about an hour ago, will add official support for SQLAlchemy as a ‘contrib’ option. According to the plans laid out by Adrian and Robin, the SQLAlchemy …