I had the same problem with phpgedview showing individuals born in 1860 and having a death date in theier records as private after installing v2.12 the first time. (The normal version not mysql)
Problem disappeared after rebuilding the indexes by the admin menu.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The big problem with marriages is that they require looking up the family record and pulling the marriage date out of there. But I suppose that since it is now being calculated at buildindex time after all of the records have been cached, I could easily look in the family record for a marriage date as well without slowing down the performance.
The import gedcom time is much slower because of the isdead calculation. Perhaps, instead of precalculating it, I could update the tables the first time it is requested. The first access of that person would be slow, but all subsequent accesses would be faster.
To fix the add user problem. Edit authentication.php and add the following line to the getUser function after $res = dbquery($sql); (about line 211):
if (mysql_num_rows($res)==0) return false;
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't have a strong opinion of when the isdead calculation should be performed. My import of 5800 INDI takes about 25sec (P4-2GHz RH9.) This time is still significantly less than the non-MySQL v2.11 import. I would go with what is easier to maintain. I don't know the range of gedcom filesizes of your user base. But it seems from earlier reading that I am on the high end.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I loaded v2.12 on a virgin RH9 system.
1) useradmin.php: I cannot add users. When I try I get Duplicate Username error. I can enter the user manually into the db table.
2) importgedcom.php: time is much longer than in v2.11 mysql version. The new dead calculation takes about 4x the import.
3) The nits that I complained about in 2.11 are all working correct.
Having the same problem with the adding users in v2.12 mysql.
Also some people are showing up as private probably due to no birth or death date even though there is a marriage date of 1694.
Is there a way to fix this or should I put a something like "BEF 1684" for the birth date to remove the private.
Everything else seems to be working good.
Steve
I had the same problem with phpgedview showing individuals born in 1860 and having a death date in theier records as private after installing v2.12 the first time. (The normal version not mysql)
Problem disappeared after rebuilding the indexes by the admin menu.
The big problem with marriages is that they require looking up the family record and pulling the marriage date out of there. But I suppose that since it is now being calculated at buildindex time after all of the records have been cached, I could easily look in the family record for a marriage date as well without slowing down the performance.
The import gedcom time is much slower because of the isdead calculation. Perhaps, instead of precalculating it, I could update the tables the first time it is requested. The first access of that person would be slow, but all subsequent accesses would be faster.
To fix the add user problem. Edit authentication.php and add the following line to the getUser function after $res = dbquery($sql); (about line 211):
if (mysql_num_rows($res)==0) return false;
--John
John
Add user fix works great.
I don't have a strong opinion of when the isdead calculation should be performed. My import of 5800 INDI takes about 25sec (P4-2GHz RH9.) This time is still significantly less than the non-MySQL v2.11 import. I would go with what is easier to maintain. I don't know the range of gedcom filesizes of your user base. But it seems from earlier reading that I am on the high end.
The fix worked for me also, Thanks
The marriage lookup would be good idea if it doesn't slow the system down.
Steve