On Tuesday 20 May 2008 21:19, Ian Clarke wrote:
> On Tue, May 20, 2008 at 3:09 PM, Matthew Toseland
> wrote:
> > On Tuesday 20 May 2008 20:46, bbackde at googlemail.com wrote:
> >> Uh? You have to mark in-memory objects as unused to get rid of them?
> >
> > No, on-disk ones. Because db4o is
Uh? You have to mark in-memory objects as unused to get rid of them?
On Tue, May 20, 2008 at 9:40 PM, Matthew Toseland
wrote:
> On Monday 19 May 2008 15:24, Matthew Toseland wrote:
>> On Monday 19 May 2008 14:47, Matthew Toseland wrote:
>> > On Monday 19 May 2008 11:34, Matthew Toseland wrote:
On Tuesday 20 May 2008 20:46, bbackde at googlemail.com wrote:
> Uh? You have to mark in-memory objects as unused to get rid of them?
No, on-disk ones. Because db4o is query-oriented, it doesn't know what objects
you want and what you don't.
>
> On Tue, May 20, 2008 at 9:40 PM, Matthew Toseland
On Monday 19 May 2008 15:24, Matthew Toseland wrote:
> On Monday 19 May 2008 14:47, Matthew Toseland wrote:
> > On Monday 19 May 2008 11:34, Matthew Toseland wrote:
> > > On Sunday 18 May 2008 19:44, Ian Clarke wrote:
> > > >
> > > > Looking at the manual, it looks like Perst operates at a lower
Matthew Toseland a ?crit :
> On Monday 19 May 2008 18:02, Julien Cornuwel wrote:
>> Matthew Toseland a ?crit :
>>
>>> Thoughts? IMHO backups are an important feature, and they'd probably have
> to
>>> be hot backups for our usage... but then, not corrupting on running out of
>>> disk space is
On Monday 19 May 2008 15:24, Matthew Toseland wrote:
On Monday 19 May 2008 14:47, Matthew Toseland wrote:
On Monday 19 May 2008 11:34, Matthew Toseland wrote:
On Sunday 18 May 2008 19:44, Ian Clarke wrote:
Looking at the manual, it looks like Perst operates at a lower level
than
Uh? You have to mark in-memory objects as unused to get rid of them?
On Tue, May 20, 2008 at 9:40 PM, Matthew Toseland
[EMAIL PROTECTED] wrote:
On Monday 19 May 2008 15:24, Matthew Toseland wrote:
On Monday 19 May 2008 14:47, Matthew Toseland wrote:
On Monday 19 May 2008 11:34, Matthew
On Tuesday 20 May 2008 20:46, [EMAIL PROTECTED] wrote:
Uh? You have to mark in-memory objects as unused to get rid of them?
No, on-disk ones. Because db4o is query-oriented, it doesn't know what objects
you want and what you don't.
On Tue, May 20, 2008 at 9:40 PM, Matthew Toseland
[EMAIL
On Tue, May 20, 2008 at 3:09 PM, Matthew Toseland
[EMAIL PROTECTED] wrote:
On Tuesday 20 May 2008 20:46, [EMAIL PROTECTED] wrote:
Uh? You have to mark in-memory objects as unused to get rid of them?
No, on-disk ones. Because db4o is query-oriented, it doesn't know what objects
you want and
On Tuesday 20 May 2008 21:19, Ian Clarke wrote:
On Tue, May 20, 2008 at 3:09 PM, Matthew Toseland
[EMAIL PROTECTED] wrote:
On Tuesday 20 May 2008 20:46, [EMAIL PROTECTED] wrote:
Uh? You have to mark in-memory objects as unused to get rid of them?
No, on-disk ones. Because db4o is
Matthew Toseland a ?crit :
> Thoughts? IMHO backups are an important feature, and they'd probably have to
> be hot backups for our usage... but then, not corrupting on running out of
> disk space is important too!
I just rewrote the WoT plugin to use db4o and I must say I like it. My
code is
On Monday 19 May 2008 18:02, Julien Cornuwel wrote:
> Matthew Toseland a ?crit :
>
> > Thoughts? IMHO backups are an important feature, and they'd probably have
to
> > be hot backups for our usage... but then, not corrupting on running out of
> > disk space is important too!
>
> I just
On Monday 19 May 2008 14:47, Matthew Toseland wrote:
> On Monday 19 May 2008 11:34, Matthew Toseland wrote:
> > On Sunday 18 May 2008 19:44, Ian Clarke wrote:
> > >
> > > Looking at the manual, it looks like Perst operates at a lower level
> > > than db4o - you need to manually create and
On Monday 19 May 2008 14:47, Matthew Toseland wrote:
On Monday 19 May 2008 11:34, Matthew Toseland wrote:
On Sunday 18 May 2008 19:44, Ian Clarke wrote:
Looking at the manual, it looks like Perst operates at a lower level
than db4o - you need to manually create and maintain indexes.
Matthew Toseland a écrit :
Thoughts? IMHO backups are an important feature, and they'd probably have to
be hot backups for our usage... but then, not corrupting on running out of
disk space is important too!
I just rewrote the WoT plugin to use db4o and I must say I like it. My
code is much
On Monday 19 May 2008 18:02, Julien Cornuwel wrote:
Matthew Toseland a écrit :
Thoughts? IMHO backups are an important feature, and they'd probably have
to
be hot backups for our usage... but then, not corrupting on running out of
disk space is important too!
I just rewrote the WoT
Matthew Toseland a écrit :
On Monday 19 May 2008 18:02, Julien Cornuwel wrote:
Matthew Toseland a écrit :
Thoughts? IMHO backups are an important feature, and they'd probably have
to
be hot backups for our usage... but then, not corrupting on running out of
disk space is important too!
17 matches
Mail list logo