From: Stef B. <st...@bo...> - 2008-03-16 09:47:51
|
Stef Bon wrote: > Hello, > > now I can check the flow of what happens (by activating debugging). It's > much more clear now. > > But when I look at query_inode_full, I do not understand what happens > there at all. > The purpose of this function is to translate a path into a inode, right? > But it does much more things. > It "returns" a table nlinks, the inode, the parent. (and more?) > > Can someone explain why this is? It runs complicated queries.... > Ok, now I've read it a couple of times, I understand it more or less. A (long) query is constructed to determine the inode, with the help of a LEFT JOIN. This query does grow bigger as the path is longer (deeper). I'm looking into the mysql syntax now. Any hints about it welcome. Stef Bon |