closures - reuse Criteria in Grails Controller -

-

typically have following last line in grails generated controller list method:

[userinstancelist: user.list(params), userinstancetotal: user.count()]

if want restrict users specific criteria looks like

[userinstancelist: user.list(params) {    ilike('login', '%test%')  }, userinstancetotal: user.count() {    ilike('login', '%test%')  }]

but violates dry principle - best way reuse criteria closure?

paged results criteria builder (the result class pagedresultlist) have property, totalcount, can use calling count() on same criteria:

def userinstancelist = user.createcriteria().list(params) {     ilike 'login', '%test%' } [userinstancelist: userinstancelist, userinstancetotal: userinstancelist.totalcount]

Comments

Post a Comment

Popular posts from this blog

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ...
Read more

c++ - Warning : overflow in implicit constant conversion -

-
in following program, line 5 give overflow warning expected, surprisingly line 4 doesn't give warning in gcc: http://www.ideone.com/u0bxn int main() { int = 256; char c1 = i; //line 4 char c2 = 256; //line 5 return 0; } i thinking both lines should give overflow warning. or there i'm missing? the topic led me experiment this: typedef type checking? there said following(which deleted answer, because when run it, didn't show had expected): //however, you'll warning case: typedef int t1; typedef char t2; t1 x = 256; t2 y = x; //possible overflow warning! (but doesn't give warning :() -wall doesn't include many options. -wconversion 1 of them , warns behavior you're interested in. see http://gcc.gnu.org/onlinedocs/gcc/warning-options.html
Read more