Hello, > Eric Leblond wrote: >> DB output plugins have been modified to use function instead of >> procedure. >> This patch convert the conntrack insertion procedure to function. > > Where is the client code that uses the returned value of the INSERT_CT > function? It's not yet developed ;) In fact, this change has been done to be in sync with a modification in the packet logging infrastructure which uses a function. If we have a function and a procedure we could not use the same SQL request prefix. We should have add an option to be able to set the correct prefix. This is quiet painfull if you consider that having a function can be useful : as it returns the ID of the packet if could be used by a third party application which use the same database. For example, it could use it to log packet : - Call to the function INSERT_CT - Do other treatment Furthermore, it seems that PROCEDURE is not trully a SQL thing only FUNCTION are defined. BR, -- Eric Leblond INL : http://www.inl.fr NuFW, Now User Filtering Works (http://www.nufw.org) -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
