Hi guys,
I've been heavily swamped with work for college, so I missed this
thead and the few others on multiple databases. Sorry.
I have implemented a proof-of-concept database scaling solution for
Django. It tackles all kind of scaling issues I have seen in Django.
It's purpose is mainly to fin
repo
> tp play with too and I'll sort it out for you.
>
> Cheers,
> Ben
>
> 2008/7/8 Jan Oberst <[EMAIL PROTECTED]>:
>
>
>
>
>
> > Hi guys,
>
> > I've been heavily swamped with work for college, so I missed this
> > thead and th
On Sep 10, 7:53 pm, Simon Willison <[EMAIL PROTECTED]> wrote:
> Dealing with single queries that span multiple databases
>
>
> Once you have different tables living in different databases there's
> always the chance that someone will try to
On Sep 22, 10:25 pm, Simon Willison <[EMAIL PROTECTED]> wrote:
> CSRF[1] is one of the most common web application vulnerabilities, but
> continues to have very poor awareness in the developer community.
> Django ships with CSRF protection in the form of middleware, but it's
> off by default. I'm
On Sep 23, 1:53 am, Tai Lee <[EMAIL PROTECTED]> wrote:
> On Sep 23, 9:27 am, Simon Willison <[EMAIL PROTECTED]> wrote:
>
> > The significant downside is that having a render() method on a form
> > that performs the same function as render_to_response feels really,
> > really strange. It's convenie
On Sep 23, 6:13 pm, oggy <[EMAIL PROTECTED]> wrote:
> Could we just include something like a signed salt+timestamp
> +REMOTE_ADDR in a hidden field? It's not exactly bulletproof because
> of the possibility of a same-IP-CSRF (affecting people behind
> proxies), but it's dead simple and doesn't req
On Sep 21, 10:29 pm, Matt Boersma <[EMAIL PROTECTED]> wrote:
> On Sep 21, 2007, at 2:22 PM, SmileyChris <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Sep 19, 11:44 pm, Ned Batchelder <[EMAIL PROTECTED]> wrote:
> >> Now we just need to get someone to put it on the site...
>
> > +1. Easy to do, looks good
> Does this differ from just using a slice does?
>
>foo = MyModel.objects.all()[0]
>
latest() involves an automated ORDER BY after the field you specified
in Meta's get_latest_by. So it would do the same as a slice[0], if you
sorted it correctly.
--~--~-~--~~~---~-
