Re: Problem while writing new backend support

Hi, Its the other way around, the database for sure does support unicode, the driver does not handle it as of yet, which is planned for shortly. The database is DB2. Did not know i was concealing that. Regards, Ambrish Bhargava --~--~-~--~~~---~--~~ You received

Re: SessionWizard

So far I've refactored a bunch of the methods to store less in the session, and generate more on demand (otherwise you could change the method and then session data represents inaccurate information). I've completedly redesigned the pages storage so it's just storing valid and verified in the

SessionWizard

So I needed the ability to specify initial data for a wizard, and I also liked the idea of storing it in the session (vs the POST). I was pointed to the SessionWizard patch, and I believe this was a 1.1 possibility as well, so I figured I'd bring up the numerous issues. First and foremost, the

Re: Make django debug page simple when develop ajax page(with firebug)

> I think we can have a configure key in settings in the future. The > developers can choose which style of debug page to use, by which type > application they're developing. Have you tried DEBUG_PROPAGATE_EXCEPTIONS [1]? [1]

CSRF / SafeForm

Hi all, I'm thinking about 'championing' this thing, having just done a bit more work on the existing CsrfMiddleware [1], and I've done some more thinking about the different issues. LONG email, sorry, this is quite complex stuff. == First == Simon suggested that the current middleware

Re: Problem while writing new backend support

On Wed, Dec 3, 2008 at 6:14 AM, Ambrish Bhargava <[EMAIL PROTECTED]> wrote: > Now I am facing problem in unicode. There are few test cases in > regression test suite which are expecting unicode results. But with > this backend, unicode is not supported and hence I am getting > failures. Is there

Re: Problem while writing new backend support

Hi, Thanks for the previous help. Now I am facing problem in unicode. There are few test cases in regression test suite which are expecting unicode results. But with this backend, unicode is not supported and hence I am getting failures. Is there a way by which I can over come this unicode

Re: Make django debug page simple when develop ajax page(with firebug)

On Wed, Dec 3, 2008 at 3:31 AM, David Cramer <[EMAIL PROTECTED]> wrote: > > I'll agree 100% that a request.is_ajax() hook to output some > simplified data would be awesome. > > On Dec 2, 10:42 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > Perhaps a better solution would be to vary

Re: Dynamically Altering Settings

On Dec 3, 4:52 pm, Kyle Fox <[EMAIL PROTECTED]> wrote: > Yes, we're using mod_wsgi  But I'm not sure that approach saves us > much because I'd still need to write a WSGI file for every site. > > (This might be because of my lack of mod_wsgi-fu, but wouldn't I also > need a VirtualHost directive

Re: Make django debug page simple when develop ajax page(with firebug)

I'll agree 100% that a request.is_ajax() hook to output some simplified data would be awesome. On Dec 2, 10:42 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Perhaps a better solution would be to vary based on request.is_ajax(). > > Alex > > On Dec 2, 11:37 pm, kernel1983 <[EMAIL