… to store long values
#### Pre-Submission Checklist - [x] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] 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: - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description During usage i can see errors in logs related to long values cannot be saved in PostgreSQL. This PR is fix for PostgreSQL and other similar databases. You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1723
-- Commit Summary --
* utils/kamctl: Adjusted avalue column in location_attrs tables to store long values
-- File Changes --
M utils/kamctl/db_sqlite/usrloc-create.sql (2) M utils/kamctl/mysql/usrloc-create.sql (2) M utils/kamctl/oracle/usrloc-create.sql (2) M utils/kamctl/postgres/usrloc-create.sql (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1723.patch https://github.com/kamailio/kamailio/pull/1723.diff
This needs to be done a bit differently: the database tables are defined inside xml files from src/lib/srdb1/schema/, changes to table structures have to be done there and then run `make dbschema`.
Thanks you Daniel @miconda PR is updated
Thanks! Ultimately I pushed a different commit, in order to define entities for sizes of the columns.
Closed #1723.