Dan McGee 7c91c59245 Remove Dummy Package concept ... Instead, we just store dependencies directly in the PackageDepends table. Since we don't use this info anywhere besides the package details page, there is little value in precalculating what is in the AUR vs. what is not. An upgrade path is provided via several SQL statements in the UPGRADING document. There should be no user-visible change from this, but the DB schema gets a bit more sane and we no longer have loads of junk packages in our tables that are never shown to the end user. This should also help the MySQL query planner in several cases as we no longer have to be careful to exclude dummy packages on every query. Signed-off-by: Dan McGee <dan@archlinux.org> Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>		2011-04-03 22:59:32 +02:00
..
aur-schema.sql	Remove Dummy Package concept	2011-04-03 22:59:32 +02:00
gendummydata.py	gendummydata.py: Do not touch output file until we need it.	2011-03-30 10:27:23 +02:00
reloadtestdb.sh	Allow DB connection values to come from the environment	2011-03-04 10:29:14 +01:00