Re: Django, initial data and custom SQL

Hello folks, On Feb 12, 8:49 am, Ludvig Ericson wrote: > On Feb 12, 2009, at 07:48, Russell Keith-Magee wrote: > > > On Thu, Feb 12, 2009 at 2:54 PM, Ludvig Ericson > > wrote: > > >> I fail to see how "it has consequences for existing code",

Re: Django, initial data and custom SQL

On Feb 10, 5:07 pm, Johan Bergström <b...@bergstroem.nu> wrote: > Hey, > > On Feb 10, 4:51 pm, "ludvig.ericson" <ludvig.eric...@gmail.com> wrote: > > > > > > > On Feb 10, 1:13 pm, Johan Bergström <b...@bergstroem.nu> wrote: > >

Re: Django, initial data and custom SQL

Hey, On Feb 10, 4:51 pm, "ludvig.ericson" <ludvig.eric...@gmail.com> wrote: > On Feb 10, 1:13 pm, Johan Bergström <b...@bergstroem.nu> wrote: > > > Since Django executes my custom SQL before creating indexes, it's > > impossible to achieve somethi

Django, initial data and custom SQL

do, what I would like to know is if there's a reason to why custom SQL is executed before index creation. Kind regards, Johan bergström --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers&

Django, Simplejson and speedups

Simplejson has been getting some version increments lately and Django hasn't been including them (there are tickets), which is - in my opinion - okay. Constantly upgrading the included simplejson library is an never ending rabbit chase where required effort doesn't motivate possible benefits

Re: Django & memcache hashing

On Nov 20, 8:58 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2008-11-20 at 07:20 +0300, Ivan Sagalaev wrote: > > Malcolm Tredinnick wrote: > > > Okay. If we go this path, it's something to include in Django, rather > > > than recommending yet another caching package. We either

Re: Pluggable filestorage [was Heads-up: doing a bit of triage work]

On Sep 18, 1:21 pm, "Marty Alchin" <[EMAIL PROTECTED]> wrote: > On 9/18/07, Johan Bergström <[EMAIL PROTECTED]> wrote: > > > What is wrong with using FTP for intranet file shuffling? I don't > > think frameworks should decide or advocate how you design yo

Re: Pluggable filestorage [was Heads-up: doing a bit of triage work]

towards SFTP is in my opinion the way forward. > The is the same reasoning behind not shipping with a CGI handler -- > Django shouldn't make it easy to do stupid things. I don't think this is the same thing. Why use encryption when you trust the sender? > Now, a SSH/SFTP backend... th

Re: Decouple simplejson from Django?

be solved on a similar fashion as above. thanks, Johan Bergström --~--~-~--~~~---~--~~ 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@google

Re: Decouple simplejson from Django?

> Can you use the ORM without a database adapter? Ok, that might sound a bit stupid since you already kind of answered that in the post above. What i meant was that Django has lot of different imports, and without some of them (say a database adapter) Django is crippled. I personally don't see

Re: Decouple simplejson from Django?

On Jul 12, 8:55 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > The other modules you mention are optional to a certain extent (don't > technically need flup to do Django-as-WSGI, can use Django without a > database or with your choice of DB adapter), but simplejson is > absolutely required

Decouple simplejson from Django?

) cheers, Johan Bergström --~--~-~--~~~---~--~~ 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,

Re: make db form settings

I recently made a patch that can be used to get a similar result. You can find the patch here: http://code.djangoproject.com/ticket/4528 regards, Johan Bergström On Jul 4, 7:54 pm, Carl Karsten <[EMAIL PROTECTED]> wrote: > I have the begging of something that may eventually get