resolve_d inserts

mysql.dump and pgsql.dump have different values in resolve_d.

I was trying to find out why MySQL would say new bugs where UNRESOLVED and
in PostgreSQL they said it was OPEN in the reports query. I see in
postbug.php bugs.resolve=4 by default.

I find this in anthill/etc:

[email protected] etc $ grep -ri resolve_d *.dump| grep INSERT
mysql.dump:INSERT INTO resolve_d (id, name) VALUES (0,'FIXED');
mysql.dump:INSERT INTO resolve_d (id, name) VALUES (1,'INVALID');
mysql.dump:INSERT INTO resolve_d (id, name) VALUES (2,'WONTFIX');
mysql.dump:INSERT INTO resolve_d (id, name) VALUES (3,'DUPLICATE');
pgsql.dump:INSERT INTO resolve_d (id, name) VALUES (0,'FIXED');
pgsql.dump:INSERT INTO resolve_d (id, name) VALUES (1,'INVALID');
pgsql.dump:INSERT INTO resolve_d (id, name) VALUES (2,'WONTFIX');
pgsql.dump:INSERT INTO resolve_d (id, name) VALUES (3,'DUPLICATE');
pgsql.dump:INSERT INTO resolve_d (id, name) VALUES (4,'OPEN');


Notice PostgreSQL has 4 "OPEN", MySQL doesn't.


Russell Valentine

_______________________________________________
Anthill-workers mailing list
Anthill-workers-+mQDA36h6dWw5LPnMra/[email protected]
http://vmlinuz.ca/mailman/listinfo/anthill-workers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/xr2RO0EDJO5MgRYRAvLAAJ4hRH1ivUumJvP4dKgWv8a8XUkJ1QCeIM0h
OpKiVUuLp77UdT3MlIn7AmE=
=1P3P
-----END PGP SIGNATURE-----