I want to select all fields from a table where the id does not match with one of the List values. I can find those who match easily but what about in opposite way?

@Query("SELECT * table W,java,android,android-room"/>
	














    

		

        

            
            时间戳
        

		

		

        
		

    
















	
首页  > 解决方案 > 是否有与 WHERE 字段 IN (:List)

I want to select all fields from a table where the id does not match with one of the List values. I can find those who match easily but what about in opposite way?



@Query("SELECT * table W












java - 是否有与 WHERE 字段 IN (:List)

I want to select all fields from a table where the id does not match with one of the List values. I can find those who match easily but what about in opposite way?



@Query("SELECT * table W





问题描述



I want to select all fields from a table where the id does not match with one of the List values. I can find those who match easily but what about in opposite way?



@Query("SELECT * table WHERE id IN (:listOfIds)")
List<TableObject> selectOpposite(List<Integer> listOfIds);








Go worker pattern for warm workers


I'm working on a problem where I have a set of "warm workers". That means that they are maintained in memory, maintain their own contexts and are callable. I've been looking at various Go worker implementations but all depend on closures or simple calculation functions that return results.



I found an example of a worker that lets me spin up my contexts and distribute tasks to them based on a max queue and max routine limit: https://github.com/cahitbeyaz/job-worker/blob/master/main.go#L131



However this pattern doesn't allow me to return a result from the context and feed it back. I'm also using a web server and so the web handler has to receive the result and respond accordingly.



Is there a specific/better pattern I should/could follow or a way I could adapt the job-worker example?



PS. At first I thought I could create a ResultQueue where results are pushed back and consumed by the web handler. I don't think the ordering of the queue can be counted on though.


标签： javaandroidandroid-room


解决方案









Simply use NOT IN instead of IN.










推荐阅读