> LPP> I took a look at it. CURSOR-FETCH-QUERY is complicated enough as it > LPP> is, so let's reduce it to some common primitives as far as possible > LPP> and implement our NULL cases manually. > > it seems only it's where-generating part needs to be replaced (as well as > parameters value-compare and key-compare), > or you have some other restructuring in mind?
That's exactly what I had in mind. > i don't see some clear patter here, so we can just explicitly pass where > part to cursor-fetch-query function. Yes. > also i have some concerns that postgres might fail to optimize bigger > conditionals in where.. You might be right here, but I suppose that this type of WHERE clause with NULL checks might be optimized. We can compare benchmarks to be sure. Leslie _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
