From: Sucheta T. <su...@vb...> - 2004-11-22 18:41:42
|
Well, As Josef rightly pointed , I guess that can go to description instead of name field. Though I don't find a clear demarcation between the two. For example in this case: cold inducible similar to other osmotic stress induced gene products includin: Tomato abscisic stress ripening protein 1 encoded by GenBank Accession Number L08255, Solanum lycopersicum ABA- and ripening-induced protein encoded by GenBank Accession Number L20756 and to Solanum chacoense abscisic stress ripening protein encoded by GenBank Accession Number U12439 [Solanum tuberosum] This happens when I give a --regex_source_id="gi\|(\w+)\|(.*)" --regex_secondary_id="gb|emb|dbj|ref|pir|sp\|(\w+)" --regex_name=".*\|(.+)$" in the insertnewexternalsequence plugin. At 01:20 PM 11/22/2004 -0500, Steve Fischer wrote: >can you provide an example of such a name? > >steve > >Sucheta Tripathy wrote: > >>Dear group, >> >>I am now uploading data to the externalaasequence, and frequently it gets >>interrupted because the name has data type varchar2(255), where as some of >>the names are much longer than that.I was wondering if the table >>definition can be changed in the distribution to handle this OR is there a >>reason why this should be kept as varchar2(255)? >> >>Thanks >> >>Sucheta >> >> |