Tak się własnie zastanawialem, czy operujac na streamie, nie wywołamy pośrednio n+1 jak w przypadku normalnej iteracji
spring.jpa.show-sql = true
wywoluje metode:
RegisteredUser tweetOwner = userRepository.findOne((long)1);
tweetOwner
.getTweets()
.forEach(System.out::println);
logi
Hibernate: select registered0_.user_id as user_id1_0_0_, registered0_.email as email2_0_0_, registered0_.first_name as first_na3_0_0_, registered0_.last_name as last_nam4_0_0_, registered0_.password as password5_0_0_, registered0_.www as www6_0_0_, roles1_.registered_user_id as register3_1_1_, roles1_.role_id as role_id1_1_1_, roles1_.role_id as role_id1_1_2_, roles1_.role as role2_1_2_, roles1_.registered_user_id as register3_1_2_ from registered_user registered0_ left outer join role roles1_ on registered0_.user_id=roles1_.registered_user_id where registered0_.user_id=?
Hibernate: select tweets0_.user_id as user_id4_2_0_, tweets0_.tweet_id as tweet_id1_2_0_, tweets0_.tweet_id as tweet_id1_2_1_, tweets0_.content as content2_2_1_, tweets0_.score as score3_2_1_, tweets0_.user_id as user_id4_2_1_ from tweet tweets0_ where tweets0_.user_id=?
twitter.model.Tweet@75b20340
twitter.model.Tweet@647ab628
twitter.model.Tweet@2a2fecf8
twitter.model.Tweet@18a046aa
twitter.model.Tweet@207dccd1
twitter.model.Tweet@7e75391b
twitter.model.Tweet@1bb88d96
czyli nie ma n+1,