### Description
I came across the following while trying to serialize SQL data to xavp (`sql_xquery()`) and then serializing the result to htable using `xavp_params_implode()`. One of the data columns has a type of `BIGINT`. The resulting string had neither the key nor value.
I recognize that Kamailio does not currently have support for 64 bit integers and that adding support for it is probably not a trivial matter. My request here is really that if the value is going to be dropped it would be good if `pv` would omit a warning.
#### Reproduction
MySQL table:
```sql
CREATE TABLE dids (
id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
did varchar(11) NOT NULL,
route_id BIGINT NOT NULL,
failure_route_id INT NOT NULL,
description VARCHAR(255)
);
```
With data like this:
```sql
INSERT INTO dids
( did, route_id, failure_route_id, description ) VALUES
( '15555551000', 101, 1006, 'Alice' );
```
And the following Kamailio code:
```
$var(query) = "SELECT * "
+ "FROM dids "
+ "WHERE did = " + $(rU{sql.val.str});
sql_xquery("db", "$var(query)", "did_data");
xavp_params_implode("did_data", "$sht(did=>$rU)");
xinfo("Serialized query result: [$sht(did=>$rU)]\n");
```
The following log line results - the `route_id` is missing all together:
```
1(7) INFO: <script>: Serialized query result: [id=1;did=15555551000;failure_route_id=1006;description=Alice;]
```
### Possible Solutions
It's worth noting that the value is usable out of the XAVP. `$xavp(did=>route_id)` is retrievable, and the problem seems to be only when running `xavp_params_implode()`. In a perfect world, the key and value would be retained and put into the serialized data, however I'm not sure of the complexity of this (what if the the value exceeds a 32 bit int?, etc). With that said, my only real request would be that if a value is dropped that a warning is omitted with a rough explanation of the reason ("omitting _keyName_ unknown_ data type", etc).
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
5.7.3
```
* **Operating System**:
Alpine 3.18
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3663
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3663(a)github.com>
#### Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #3464
#### Description
fixed rabbitmq-c deprecation warning
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3670
-- Commit Summary --
* rabbitmq: fixed rabbitmq-c deprecation warning
* kazoo: fixed rabbitmq-c deprecation warning
-- File Changes --
M src/modules/kazoo/Makefile (4)
M src/modules/kazoo/kz_amqp.c (9)
M src/modules/kazoo/kz_amqp.h (5)
M src/modules/rabbitmq/Makefile (4)
M src/modules/rabbitmq/rabbitmq.c (7)
M src/modules/rabbitmq/utils.c (6)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3670.patchhttps://github.com/kamailio/kamailio/pull/3670.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3670
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3670(a)github.com>
On Ubuntu, `/bin/sh` defaults to `dash` whose built-in `echo` command does not support the `-e` flag. `printf`, on the other hand, supports backslash escapes by default so we use that instead.
In passing, also clean up some messy ANSI escape codes.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3671
-- Commit Summary --
* utils: Prefer `printf` over `echo -e`.
-- File Changes --
M pkg/kamailio/obs/kamailio.init (2)
M utils/kamctl/kamctl (2)
M utils/kamctl/kamctl.base (10)
M utils/kamctl/kamdbctl (6)
M utils/kamctl/kamdbctl.base (10)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3671.patchhttps://github.com/kamailio/kamailio/pull/3671.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3671
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3671(a)github.com>
Module: kamailio
Branch: master
Commit: 8d3d53f5f698da1357c3475ae136677099b2f702
URL: https://github.com/kamailio/kamailio/commit/8d3d53f5f698da1357c3475ae136677…
Author: Sean Bright <sean(a)seanbright.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2023-12-12T10:38:06+01:00
utils: Prefer `printf` over `echo -e`.
On Ubuntu, `/bin/sh` defaults to `dash` whose built-in `echo` command
does not support the `-e` flag. `printf`, on the other hand, supports
backslash escapes by default so we use that instead.
In passing, also clean up some messy ANSI escape codes.
---
Modified: pkg/kamailio/obs/kamailio.init
Modified: utils/kamctl/kamctl
Modified: utils/kamctl/kamctl.base
Modified: utils/kamctl/kamdbctl
Modified: utils/kamctl/kamdbctl.base
---
Diff: https://github.com/kamailio/kamailio/commit/8d3d53f5f698da1357c3475ae136677…
Patch: https://github.com/kamailio/kamailio/commit/8d3d53f5f698da1357c3475ae136677…