Re: resolve_d inserts

On Nov 27, 2003, at 20:14, Russell Valentine wrote:

> 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.

Ooops... good catch.  Fixed in CVS now.

I'll get to your other notes about the postgres stuff hopefully 
tomorrow...  I'm mucking with FreeBSD 5.2 on my x86 laptop (where I did 
have Mandrake installed and was using it to test the postgres stuff).  
I need to get postgres installed on my powerbook first.

Been too busy with work and some real life stuff that came up... I'm 
going to try to get it figured out tomorrow, but it might be Tuesday as 
I have some Linux kernel work and a funeral to deal with.

---
MandrakeSoft Security; http://www.mandrakesecure.net/
Online Security Resource Book; http://linsec.ca/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD}

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