Summary: | Sqlite cache backend for portage | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Karol Wojtaszek (RETIRED) <sekretarz> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | radek, tomk |
Priority: | High | Keywords: | Inclusion |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
initialize database
modules file sql portage-sqlite/portage_db_sqlite.py |
Description
Karol Wojtaszek (RETIRED)
2004-05-29 00:21:38 UTC
Created attachment 32234 [details]
initialize database
Created attachment 32235 [details]
modules file
Created attachment 32236 [details]
sql
Created attachment 32237 [details]
portage-sqlite/portage_db_sqlite.py
Comment on attachment 32234 [details] initialize database >#!/bin/bash > >cat portage-sqlite-init-db.sql | sqlite /var/cache/edb/sqlite-cache Comment on attachment 32234 [details] initialize database >#!/bin/bash > >cat portage-sqlite-init-db.sql | sqlite /var/cache/edb/sqlite-cache2 cat portage-sqlite-init-db.sql | sqlite /var/cache/edb/sqlite-cache Init.sh should create /var/cache/edb/sqlite-cache not sqlite-cache2 :) Requirements: The module needs to be self-contained. It need to be able to create or alter the tables itself without user intervention. Caching backend design will be changing in such a way that a backend will be queriable rather than just a glorified file system. Will integrate new backends at that time. |