PedigreeQuery Is Not Keeping Up to Date
Moderators: Roguelet, hpkingjr, WaveMaster
Lucy wrote:While I see your point Jellac, there may be just as many folks who prefer the alphabetical default....or even some who would prefer it sorted by earnings.
Perhaps a better solution would be to give users the ability to set personal 'sort by' preferences, rather than changing the defaults for everyone.
I think chronological default is a good idea. That is the way it is listed in the JC and Brisnet db's. Just my rapidly losing value two cents!
- karenkarenn
- Breeder's Cup Winner
- Posts: 2145
- Joined: Sun Aug 03, 2008 3:01 pm
- Location: Planet Earth
- Contact:
-
- Grade II Winner
- Posts: 1277
- Joined: Tue Dec 07, 2004 10:14 am
-
- Weanling
- Posts: 28
- Joined: Fri Jun 09, 2006 2:28 pm
KonaNative wrote:I've entered Queen of Hearts/Thunder Gulch/Betrayer into the data base.
How long before I can pull up the pedigree ?
You should be able to view a pedigree right away, but in this case the horse was not entered succesfully.
Here she is:
http://www.pedigreequery.com/queen+of+hearts13
It will take a day or two before you can find her in her parents' progeny queries.
-
- Weanling
- Posts: 43
- Joined: Sat Aug 30, 2008 5:35 pm
- Location: Pennsylvania
A server hosts a database so if a server fails then everything is lost. A server cannot selectively corrupt fields within a database table. That being said, a database table can become corrupt and it seems that is the case. I would suggest that someone take a look at the database indexes and see if the links have been "broken". I suspect that is what happened, and in reality, if it is fixed, everything will come back.
A database does not live across multiple servers so it is not the server or servers that have caused this problem.
A database does not live across multiple servers so it is not the server or servers that have caused this problem.
Tappiano wrote:A server hosts a database so if a server fails then everything is lost. A server cannot selectively corrupt fields within a database table. That being said, a database table can become corrupt and it seems that is the case. I would suggest that someone take a look at the database indexes and see if the links have been "broken". I suspect that is what happened, and in reality, if it is fixed, everything will come back.
A database does not live across multiple servers so it is not the server or servers that have caused this problem.
Well put. Does the database here get backed up? A restored backup from before the database corruption would fix the problem.