Open grololo06 opened 3 years ago
jiho
commented
3 years ago Yes, the pattern should be forbidden.
In the cases above:
temporary were created there to be quick and dirty, waiting for UniEuk/WoRMS to come alongpennate, autotroph etc. should be morphobalistidae, holocentridae should be phylo.
grololo06
commented
3 years ago balistidae, holocentridae -> corrected onto EcoTaxoserver, and propagated fine to EcoTaxa. living>temporary should be Morpho, which solves the temporary issues. The rest is in WoRMS move Google sheet
grololo06
commented
3 years ago Log of execution onto ecotaxoserver. As the direct SQL does not propagate, same commands were ran onto EcoTaxa DB.
ecotaxoserver=# update taxonomy set taxotype='M' where id in (17263,17264,27675,27676,13364,13363,85234,85323,85324,85325,85326,85322,92688,92689,92230,92231,92232,85235,85244,85245,85246,85247,85248,85236,85237,85238,85239,85240,85241,85242,85243,85230,85231,85195,85196,85197,92273,92266,92304,92272,92265,11880,11879,11878,11877,11876,92271,92264,92274,92267,92306,85302,85311,85312,85313,85314,85315,85316,85317,85318,85319,85303,85304,85305,85306,85307,85308,85309,85310,85213,92323,92316,92315,92317,92320,92322,92321,92275,92268,92307,92255,85202,85203,85204,85206,85207,85208,85209,85210,85211,85212,38408,85217,85340,85346,85341,85347,85342,85348,85343,85349,85344,85350,85345,85351,92237,85337,93602,92682,92277,92270,92253,92309,92258,92312,92247,92313,92327,85263,85264,24576,85275,85276,85277,85278,85279,85280,85281,85282,85283,85266,85267,85268,85269,85270,85271,85272,85273,85284,85285,85286,85287,58306,58319,58322,85299,85300,85301,85327,85328,85329,85330,85331,85332,85333,85334,85335,58458,92269,92252,92276,92314,92256,92308,93601,92245,92236,85069,85249,85258,85259,85260,85261,85250,85251,85252,85253,85254,85255,85256,85257,27304,27303,27302,85289,85290,85291,85292,85293,85294,85295,85297,91419,85218,85219,85220,85221,85222,85223,85198,85199,85320,85321,85215,85214,85216,85226,85225,85228,85227,85224,85036,85038,85039,85037,85148,85154,85158,85229,85174,85161,85183,85163,92031,85168,92027,85298,93528,92587,92591,92603,92887,8982,92678,26325,51958,6);
UPDATE 237
Temps : 172,201 ms
ecotaxoserver=# update taxonomy set taxotype='P' where id=92329;
UPDATE 1
Temps : 0,656 ms
ecotaxoserver=# select txo.id, coalesce(txo.nbrobj,0)+coalesce(txo.nbrobjcum,0), txo.name, ptxo.id, ptxo.name
ecotaxoserver-# from taxonomy txo, taxonomy ptxo
ecotaxoserver-# where (txo.nbrobj>0 or txo.nbrobjcum>0)
ecotaxoserver-# and ptxo.id=txo.parent_id
ecotaxoserver-# and txo.taxotype='P'
ecotaxoserver-# and ptxo.taxotype='M' order by txo.id;
id | ?column? | name | id | name
----+----------+------+----+------
(0 ligne)
Temps : 64,544 ms
It looks like a Phylo taxon should not be child of a Morpho one, however:
@jiho , if it's OK with you then let's forbid the bad pattern creation. BTW, any other rule in this area?