Display Settings:

Format

Send to:

Choose Destination
See comment in PubMed Commons below
Genetics. 2006 Feb;172(2):1191-8. Epub 2005 Oct 11.

Accumulation of nonfunctional S-haplotypes results in the breakdown of gametophytic self-incompatibility in tetraploid Prunus.

Author information

  • 1Department of Horticulture, Michigan State University, East Lansing 48824, USA.

Abstract

The transition from self-incompatibility (SI) to self-compatibility (SC) is regarded as one of the most prevalent transitions in Angiosperm evolution, having profound impacts on the genetic structure of populations. Yet, the identity and function of mutations that result in the breakdown of SI in nature are not well understood. This work provides the first detailed genetic description of the breakdown of S-RNase-mediated gametophytic self-incompatibility (GSI) in a polyploid species that exhibits genotype-dependent loss of SI. Genetic analyses of six natural sour cherry (Rosaceae, Prunus cerasus) selections identified seven independent, nonfunctional S-haplotypes with disrupted pistil component (stylar-S) and/or pollen component (pollen-S) function. A genetic model demonstrating that the breakdown of SI in sour cherry is due to the accumulation of a minimum of two nonfunctional S-haplotypes within a single individual is developed and validated. Our finding that sour cherry is SI when only one nonfunctional S-haplotype is present has significant evolutionary implications since nonfunctional S-haplotypes would be maintained in the population without causing an abrupt shift to SC. Furthermore, we demonstrate that heteroallelic sour cherry pollen is self-incompatible, which is counter to the well-documented phenomenon in the Solanaceae where SC accompanying polyploidization is frequently due to the SC of heteroallelic pollen.

PMID:
16219786
[PubMed - indexed for MEDLINE]
PMCID:
PMC1456217
Free PMC Article
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Icon for HighWire Icon for PubMed Central
    Loading ...
    Write to the Help Desk