Re: [GUSDEV] An important schema question (to me, anyways)

[Josef J. <ju...@cs...>]

Chris Stoeckert <sto...@pc...> writes:
> 
> The unique constraint on source_id of AAEntry/NAEntry will be  
> eliminated in  the next release. To help me remember, please enter a  
> bug request.

Will do;

> Thanks for bringing this up.

And thank you for taking a look;


Also, something you might want to consider is putting the
fields of AAEntry/NAEntry into ExternalAASequence/ExternalNASequence
and then eliminating AAEntry/NAEntry.

As the ExternalAASequence/ExternalNASequence views are
intended to hold information on public sequences such
as those from genbank/swissprot records, then there
is no reason to keep the dates of these records
in a separate table.

I was actually struggling with finding an elegant way of
putting swissprot sequence dates into ExternalAASequence
until I stumbled upon AAEntry.

I can see no reason why the dates of these records
should be in a separate table, and actually simplifying
the schema without loosing any functionality would
be a big plus.

Thanks,

Josef