Hi Daniel, thank you for your response. Unfortunately, resetting the auto increment value is not an option for us since other backend systems are using and referencing that data. We try to avoid maintaining our own fork of kamailio and therefore I have opened a pull request here https://github.com/kamailio/kamailio/pull/3407
cheers Julius > On 27 Mar 2023, at 14:37, Daniel-Constantin Mierla <[email protected]> wrote: > > Hello, > > kamailio is not using the id column internally, you can changed as you > wish if no external/custom tools you have depend on its type. > > I think only a few modules use the id columns from their related table > (iirc, msilo and lcr), for the rest the id column is purely for > facilitating external management of those records. > > Then, I guess, another option would be to reset the auto increment value. > > Cheers, > Daniel > > On 27.03.23 13:52, Julius Flohr wrote: >> Hi, >> >> we've been using kamailio successfully for many years now and we've noticed >> that the id field in the location database of our installation (userloc >> module) will overflow in the foreseeable future. Currently it is setup as a >> INT(10). >> Are there any reasons not to change it to BIGINT and upstream that change? >> >> Cheers >> >> Julius >> _______________________________________________ >> Kamailio (SER) - Development Mailing List >> To unsubscribe send an email to [email protected] > > -- > Daniel-Constantin Mierla -- www.asipto.com > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com > Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com >
_______________________________________________ Kamailio (SER) - Development Mailing List To unsubscribe send an email to [email protected]
