XREF limitation?

Dave Matthews matthews at greengenes.cit.cornell.edu
Wed Jul 3 03:38:03 EST 2002


Hi Qunfeng Dong,

This isn't related to XREF, it's because of your tag UNIQUE.
You'd get the same result if you directly loaded

    Sequence : e
    Matching_genomic_sequence g1
    Matching_genomic_sequence g2

UNIQUE means that the field can have only one value.  In this case you want
to allow Matching_genomic_sequence to have multiple values so just remove
"UNIQUE".

- Dave

> To: bionet-software-acedb at uunet.uu.net
> Subject: XREF limitation?
> From: "Qunfeng Dong" <qfdong at iastate.edu>
> Date: Tue,  2 Jul 2002 09:31:56 +0100 (BST)
> 
> 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

---





More information about the Acedb mailing list