We developed a small patch to check if there is a second result set
when the first result set has zero rows. It's pretty specific and
probably shouldn't be merged, but might help someone else if they are
stuck in a similar situation.
modules/db_mysql/dbase.c | 13 +++--
1 file changed, 11
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
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
On Wed, Mar 18, 2020 at 5:32 PM Calvin Ellison
wrote:
> We've narrowed this
We've narrowed this down to a stored procedure that sometimes returns more
than one result set, and when that happens the first result set is empty.
It appears that db_mysql is setting the client flags to accept
multiple result sets but the only processes the first one.
Here's how my developer
Any takers? This seems like a problem with db_mysql. It sees the column
data but not the row.
Regards,
*Calvin Ellison*
Senior Voice Operations Engineer
calvin.elli...@voxox.com
On Sun, Mar 15, 2020 at 3:40 PM Calvin Ellison
wrote:
> This does not happen on every query response but will
This does not happen on every query response but will happen on every
response for the same query. CLI mysql and mariadb clients show the result
row correctly, and pcaps confirm that opensips is getting the row response
(attached).
I recompiled opensips against libmariadbclient (Ubuntu
