Re: Non-SQL database cache backend

On Tue, Nov 2, 2010 at 9:20 AM, Jonas H. wrote: > On 11/02/2010 01:09 AM, Russell Keith-Magee wrote: >> >>   - The base class refactoring makes sense, although what you're >> proposing isn't really just a 'BaseDB backend', but a 'backend that >> has to implement culling'. The

Re: Non-SQL database cache backend

On 11/02/2010 01:09 AM, Russell Keith-Magee wrote: - The base class refactoring makes sense, although what you're proposing isn't really just a 'BaseDB backend', but a 'backend that has to implement culling'. The reason I can say this is that the logic you have factored out is duplicated in

Re: Non-SQL database cache backend

On Mon, Nov 1, 2010 at 11:10 PM, Jonas H. wrote: > On 10/29/2010 03:37 PM, Russell Keith-Magee wrote: >> >> Writing a MongoDB (or any other non-SQL) cache backend shouldn't be a >> particularly onerous task; after all, the queries are simple, and the >> .The SQL backend is only

Re: Non-SQL database cache backend

On 10/29/2010 03:37 PM, Russell Keith-Magee wrote: Writing a MongoDB (or any other non-SQL) cache backend shouldn't be a particularly onerous task; after all, the queries are simple, and the .The SQL backend is only 150 lines of code; a backend for any noSQL backend should run to about the same

Re: Non-SQL database cache backend

On Fri, Oct 29, 2010 at 9:18 PM, Jonas H. wrote: > Hi folks, > > upon the recommendation on the django-nonrel mailing list, I'll re-post my > original question here: > > -- Begin original message -- > I just tried to use MongoDB as cache backend (only for development ;-) but >

Non-SQL database cache backend

Hi folks, upon the recommendation on the django-nonrel mailing list, I'll re-post my original question here: -- Begin original message -- I just tried to use MongoDB as cache backend (only for development ;-) but it failed because apparently the Django guys do hand-written SQL in the