I agree, caching should be disabled when using a DB backend. I'll look into doing that as well, though it will probably have some major impact to the search/find code.

On Jun 13, 2011 10:25 AM, "Bill Peck" <bpeck@redhat.com> wrote:
> On 06/13/2011 11:21 AM, Scott Henson wrote:
>> On Sun, 12 Jun 2011 12:07:29 +0300, Alexander Todorov<atodorov@otb.bg> wrote:
>>> На 11.06.2011 19:54, James Cammarata написа:
>>>> Anyway, let me know if you guys think this is worth pursuing or if
>>>> there's much interest in even adding support for something like this.
>>> +1 for MongoDB backend.
>> Yeah, patch gladly accepted against the master branch.
>>
>
> Does the DB backend do anything to prevent us from loading everything
> into ram? Based on your comment that it doesn't recognize changes to
> the DB I'm thinking it doesn't. So just like couchDB, this just
> changes the backend store from json files on disk to a DB.
>
> This is a great first step, but what I would really like to see is some
> smarter loaders/serializers that query the DB for the objects instead of
> loading everything into ram. Let the DB do the caching.
>
>
>>
>> _______________________________________________
>> cobbler-devel mailing list
>> cobbler-devel@lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/cobbler-devel
>