Could a VARBINARY be used here instead? We actually use a memory table for the dialog table to reduce load on our disk and it does not support BLOB or TEXT, so instead we changed it to a large VARCHAR. The mysql docs suggest you can treat a TEXT the same as a VARCHAR, but obviously there are differences.
Regards, Ryan On Wed, Dec 7, 2011 at 9:51 AM, Jayesh Nambiar <jayesh.v...@gmail.com> wrote: > Hi Razvan, > This actually solved the problem. Thank you very much. It was defined as > VARCHAR instead of TEXT. > Thank you very much for all the efforts. Really appreciate it. Need to get > hold of my DB guy for the stupid mistake !! > > --- Jayesh > > > On Wed, Dec 7, 2011 at 8:13 PM, Razvan Crainea <razvancrai...@opensips.org> > wrote: >> >> Hi, Jayesh! >> >> Can you check in your mysql database if the vars column from the dialog >> table is declared as TEXT or BLOB and not CHAR? If not, please change your >> column into BLOB: >> >> ALTER TABLE dialog CHANGE vars vars BLOB; >> >> Regards, >> >> -- >> Răzvan Crainea >> OpenSIPS Developer >> >> >> On 12/07/2011 02:27 PM, Jayesh Nambiar wrote: >>> >>> Hi Razwan, >>> >>> This is the pastebin of logs after shutdown: >>> http://pastebin.com/tvmrSqwB >>> >>> This is the pastebin of logs after start which is huge: >>> http://pastebin.com/C6K4Jt5y >>> >>> --- Jayesh > > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users