[Yum-devel] [PATCH 1/3] Add dropCachedDataPostTransaction() API and document dropCachedData().
seth vidal
skvidal at fedoraproject.org
Sat Sep 25 14:04:15 UTC 2010
On Sat, 2010-09-25 at 08:08 +0200, Tim Lauridsen wrote:
>
>
> On Fri, Sep 24, 2010 at 11:31 PM, seth vidal
> <skvidal at fedoraproject.org> wrote:
> On Fri, 2010-09-24 at 00:02 -0400, James Antill wrote:
> > Calling dropCachedData() before we are "done" is pretty bad,
> as we can
> > load a package more than once. It's also a giant perf. hit,
> esp. for
> > yumdb checksum*. So we Document all that and add a special
> API to call
> > just after a transaction has run, to cleanup just the stuff
> we want.
>
>
>
> ACK - but I sometimes wonder if moving the yumdb to sqlite
> would be
> better until/if we move to btrfs for the fs
>
> -sv
>
>
>
> _______________________________________________
> Yum-devel mailing list
> Yum-devel at lists.baseurl.org
> http://lists.baseurl.org/mailman/listinfo/yum-devel
>
>
> I remember there was some discussion about sqlite vs. filesystem as a
> db for yumdb, but cant remember why it sqlite was not selected in the
> first place. Can some one enlighten my "old" brain" :)
>
b/c of the way/type of data we'd be storing - it's more or less just
simple key-value pairs
so the sqlite db would be a very simple format like:
"""CREATE TABLE pkginfo ( pkgKey INTEGER PRIMARY KEY, pkgId TEXT,
name TEXT, arch TEXT, version TEXT, epoch TEXT, release TEXT);""",
"""CREATE TABLE yumdb ( pkgKey INTEGER, key TEXT, value TEXT);""",
also b/c it makes life really easy to add/subtract
-sv
More information about the Yum-devel
mailing list