8479716afe2a31901141de47a23bcddf06325fa3
hiram
  Thu Mar 26 17:28:55 2020 -0700
unsigned int is a poor choice for numbers that need to have operations such as subtraction on them, MySQL keeps everything in unsigned int and is confused by negative results refs #21074

diff --git src/hg/lib/asmEquivalent.sql src/hg/lib/asmEquivalent.sql
index 66be4e5..1617434 100644
--- src/hg/lib/asmEquivalent.sql
+++ src/hg/lib/asmEquivalent.sql
@@ -1,18 +1,18 @@
 # asmEquivalent.sql was originally generated by the autoSql program, which also 
 # generated asmEquivalent.c and asmEquivalent.h.  This creates the database representation of
 # an object which can be loaded and saved from RAM in a fairly 
 # automatic way.
 
 #Equivalence relationship of assembly versions, Ensembl: UCSC, NCBI genbank/refseq
 CREATE TABLE asmEquivalent (
     source varchar(255) not null,	# assembly name
     destination varchar(255) not null,	# equivalent assembly name
     sourceAuthority enum("ensembl", "ucsc", "genbank", "refseq") not null,	# origin of source assembly
     destinationAuthority enum("ensembl", "ucsc", "genbank", "refseq") not null,	# origin of equivalent assembly
-    matchCount int unsigned not null,	# number of exactly matching sequences
-    sourceCount int unsigned not null,	# number of sequences in source assembly
-    destinationCount int unsigned not null,	# number of sequences in equivalent assembly
+    matchCount bigint not null,	# number of exactly matching sequences
+    sourceCount bigint not null,	# number of sequences in source assembly
+    destinationCount bigint not null,	# number of sequences in equivalent assembly
               #Indices
     INDEX (source),
     INDEX (destination)
 );