[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/auth/provider/godb.php on line 137: Undefined array key "PHPSESSID"
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4129: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3008)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4129: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3008)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4129: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3008)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4129: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3008)
goproblems.com • Merge equals positions
Page 1 of 1

Merge equals positions

Posted: Thu Jan 14, 2010 1:10 am
by mafutrct
As far as I know, equal positions that arise by a different move order (or by passes) do not lead to the same database entry. That's an important feature that should by implemented to avoid doubled work.

Re: Merge equals positions

Posted: Sun Jan 17, 2010 3:49 pm
by adum
this is a good idea -- i have this for goproblems, and it would work well in josekipedia too. it's a bit tricky right now but someday i'd like to do it.

Re: Merge equals positions

Posted: Thu Mar 31, 2011 6:16 am
by mafutrct
status?

Re: Merge equals positions

Posted: Tue Apr 26, 2011 4:23 pm
by adum
no progress yet...

Re: Merge equals positions

Posted: Wed Feb 12, 2014 9:35 pm
by dracula
The main advantage of this feature isn't even avoiding duplicated effort but in making sure there aren't duplicates of a position having different sets of follow up moves and being seen by different eyes. Also, someone who's an expert on a certain position shouldn't have to hunt around for every example where the position comes up.

Re: Merge equals positions

Posted: Thu Sep 02, 2021 12:06 am
by k0n0
adum wrote:this is a good idea -- i have this for goproblems, and it would work well in josekipedia too. it's a bit tricky right now but someday i'd like to do it.
A user should be informed about all the variations that lead to the merged node. How do you want to achieve it?