[BioSQL-l] DBXRef

[Hilmar Lapp]

FYI and in case you were wondering what the status on this is, I still think that theoretically this would be the right way to go, but in practice there are issues caused by the fact that the DBLink adaptor's business logic doesn't know (and shouldn't have to know) that in this schema DBLink and Bio::PrimarySeq are the same thing. I.e., the skeleton update is a twist in the business logic, that I decided I don't want to get into at this point.

So, for the time being I'll keep the DBXRef table.

	-hilmar


> -----Original Message-----
> From: Hilmar Lapp 
> Sent: Thursday, September 12, 2002 1:03 PM
> To: Biosql
> Subject: [BioSQL-l] DBXRef
> 
> 
> I propose to convert the implicit foreign keys to bioentries 
> captured as DBXref into explicit foreign keys to Bioentry.
> 
> This enables integrity checking by the database, fast and simple 
> joins, and provides for easy annotation/decoration of DBXrefs 
> (because they'd become no less annotatable as any other Bioentry).
> 
> At the same time, this change would give rise to a Bioentry-Bioentry 
> association table, which we need anyway to represent relationships 
> between bioentries, one of the central concepts of the database 
> we're building here. These associations would be typed.
> 
> To extend this, eventually these relationships will also need to 
> reference evidence. If anyone has thoughts on this please share. 
> This is not our most immediate problem though.
> 
> 	-hilmar
> --
> -------------------------------------------------------------
> Hilmar Lapp                            email: lapp at gnf.org
> GNF, San Diego, Ca. 92121              phone: +1-858-812-1757
> -------------------------------------------------------------
> 
> _______________________________________________
> BioSQL-l mailing list
> BioSQL-l@open-bio.org
> http://open-bio.org/mailman/listinfo/biosql-l
>