From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] unread status
Date: Wed, 30 Dec 2009 01:24:09 +0200 [thread overview]
Message-ID: <1262128724-sup-1138@tilus.net> (raw)
In-Reply-To: <1262128268-sup-2780@tw>
Philipp Überbacher, 2009-12-30 01:12:
> Thanks, this seems to work. What's the reasoning behind explicit save?
I'd assume performance, but (at least with Xapian) it feels like a
non-issue. I'd like implicit save, or automatic save after every n
operations/seconds with $ to explicitly invoke save if the performance
really is an issue.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-12-29 23:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 14:47 Philipp Überbacher
2009-12-29 22:53 ` William Morgan
2009-12-29 23:12 ` Philipp Überbacher
2009-12-29 23:24 ` Tero Tilus [this message]
2009-12-29 23:49 ` Rich Lane
2009-12-29 23:54 ` William Morgan
2009-12-30 0:32 ` John Bent
2010-01-03 22:22 ` William Morgan
2010-03-05 15:59 ` John Bent
2010-03-05 20:00 ` John Bent
2010-03-05 20:32 ` John Bent
2009-12-29 23:33 ` William Morgan
2009-12-29 23:54 ` Philipp Überbacher
-- strict thread matches above, loose matches on Subject: below --
2009-12-29 13:45 Philipp Überbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1262128724-sup-1138@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox