Hi
Matching_genomic_sequence UNIQUE ?Sequence ...
------
nothing to do with XREF, it's the normal UNIQUE behaviour
bye
Nicolas
Qunfeng Dong wrote:
> Hi there,
>> I am wondering if I am encountering an unknown XREF limitation?
>> Given the following AceDB model
>> ?Sequence DNA UNIQUE ?DNA UNIQUE Int
> Title UNIQUE ?Text
> Other_name ?Text
> Type EST
> Genomic_sequence
> ...
> Matching_genomic_sequence UNIQUE ?Sequence XREF Matching_ESTs
> Matching_ESTs ?Sequence XREF Matching_genomic_sequence
> ...
>> Now given the following ace file
>> Sequence : g1
> Matching_ESTs e
>> Sequence : g2
> Matching_ESTs e
>> The above acefile is intended to say that the same EST sequence e
> matches both Genomic_sequence g1 and g2 (probably because g1 g2 are
> homologous seq). However, Then when this data file was loaded into
> AceDB, the database only recorded the second information g2 - e but
> flushed out the first one g1 - e.
>> Is this a known XREF limitation? If so, Any suggestions of how to overcome it?
> Thanks in advance!
>> Qunfeng Dong
>>
