We can bring this up with the vendor, but it's a 3rd party system we have no control over. I understand limiting what OpenSIPS does that isn't SIP, and it would only be safe to combine the results sets if they have the same fields. Anything else could throw an error or just return combine results sets up to the first one that's different. avp_db_query can already handle multiple rows from there.
This doesn't need to become a mainline change if no one else is interested, but I could sure use a patch to handle at least two results sets with identical columns. Regards, *Calvin Ellison* Senior Voice Operations Engineer calvin.elli...@voxox.com On Wed, Mar 18, 2020 at 3:39 PM Brett Nemeroff <br...@nemeroff.com> wrote: > You don’t want to return multiple result sets. I wouldn’t think any > support would be added for this. > > Maybe you can create a stored procedure that calls that stored procedure > and returns a single combined result set >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
