Hi,

I have understand why it's not working well :

1) the tagxtag database contains the possibly-related tags. 

As all hierarchical tag contains the same "root" tags, we have a
potentiel link between "Photographie|Friend|Dave" & "Photographie|
Animal|Cat' the sql result contains all tags...

2) the sql result make a ORDER BY tag.id so all tag are order as before
the search ...

I have propose a patch to the change to ORDER BY tagxtag.count.
(one-line patch)

Can be found on the opened bug :
        http://www.darktable.org/redmine/issues/9088

 For me, it's work as expected.

Regards

Le lundi 29 juillet 2013 à 16:34 +0200, Alexander Wagner a écrit :
> On 07/29/2013 02:23 PM, Roumano wrote:
> 
> Hi!
> 
> > Thanks you for this investigation, this mini-how-to is working for me
> > too !!!
> 
> De rien. :)
> 
> > Can you update the ticket opened for this issue with this interesting
> > information ?
> 
> Well, given some more time for investigation I might even be able to 
> come up with some working patch.
> 
> However, as mentioned, I'd need a helping hand here on the 
> menu-population issue and I need to understand the the in depth logic of 
> this tagxtag. I just guess our devs have taken their /well deserved/ 
> holidays at the moment. :)
> 




------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel

Reply via email to