1 |
Jerry McBride wrote: |
2 |
|
3 |
> Portage SHOULD have a database backend. MySql would be perfect. In the name |
4 |
> of performance, at least have a second look at this. |
5 |
|
6 |
I don't think mandating any relational database as a pre-requisite to |
7 |
Portage is a good idea, unless you implement it in such a way that you |
8 |
have it as a pluggable backend, i.e. you can stick with the current |
9 |
filesystem method, or bdb, or MySQL, or PostgreSQL, or whatever. |
10 |
|
11 |
There are some plusses to having the database backend: Centralized tree, |
12 |
and fast queries. Downside: Extra complexity, and how often do you need |
13 |
to query the tree anyway? |
14 |
|
15 |
And yes, this is my project: |
16 |
|
17 |
http://sourceforge.net/projects/mysql-python |
18 |
a.k.a. dev-python/mysql-python |
19 |
-- |
20 |
Andy Dustman <adustman@×××××××××.edu> |
21 |
Office of Information Technology, Terry College of Business, UGA |