[Bioperl-l] DBD::mysql::st execute failed: Column 'seqname' cannot be null

Dan Bolser dan.bolser at gmail.com
Fri Jan 28 13:01:28 UTC 2011


I think the bug may be due to lines like this, and the fact that my
sequence id is '0' in this case!

	$types{$type}{seqname}  ||= $seqname;


On 28 January 2011 12:08, Dan Bolser <dan.bolser at gmail.com> wrote:
> Anyone seen this? Google didn't give me any clues:
>
> ## Load feature data
> use Bio::SeqFeature::Generic;
> use Bio::DB::SeqFeature::Store;
>
> ...
>
>  my $feat = Bio::SeqFeature::Generic->
>    new( -seq_id      => 'x'
>         -source_tag  => 'dund',
>         -primary_tag => 'megascaffold',
>         -start       => 1,
>         -end         => 100,
>         -score       => 0,
>         -strand      => '+',
>         -phase       => ',',
>         -attributes  => { ID => 'x', Name => 'x' }
>       );
>
>  $db->store($feat)
>    or die "Couldn't store!";
>
>
> which gives:
>
> DBD::mysql::st execute failed: Column 'seqname' cannot be null at
> ~/perl5/lib/perl5/Bio/DB/SeqFeature/Store/DBI/mysql.pm line 1574, <>
> line 590.
> Transaction aborted because DBD::mysql::st execute failed: Column
> 'seqname' cannot be null at
> ~/perl5/lib/perl5/Bio/DB/SeqFeature/Store/DBI/mysql.pm line 1574, <>
> line 590.
> Couldn't store! at ./for_gbrowse.plx line 90, <> line 590.
>




More information about the Bioperl-l mailing list