Outer join fetch sends unnecessary SELECT to database to get parent

In a bi-directional parent-children relationship, if I call session.Find() to outer join fetch like this
IList lst = session.Find("from Parent p left outer join fetch p.Children");
I saw a SELECT...FROM Parent LEFT OUTER JOIN Children to fetch both parent object and child objects, but after it there is a SELECT...FROM Parent WHERE... to get children's parent from database. The second SQL is really not necessary since the parent has been in memory after the 1st SQL.

I don't know if the 2nd level cache can avoid the 2nd SELECT hitting database any way.