Hi Phil,
sorry for the late reply
Phil Vandry wrote:
(Sorry, I digress to MySQL issues not related to OpenSIPS. Future
replies will be off-list.)
On Tue, Mar 31, 2009 at 11:44:42AM +0300, Bogdan-Andrei Iancu wrote:
So, more or less it is about the table size - what is not clear for
On Wed, Mar 25, 2009 at 09:03:35AM +0100, Jacek Konieczny wrote:
that is not a sane way to do things. The problems will start as soon as
someone will try to process this data as 'latin1' (according to the
declaration on the database), when it is not latin1.
Agreed. And the database would be
On Tuesday 24 March 2009, Jacek Konieczny wrote:
Hello,
As I was just doing upgrade from OpenSIPs 1.4.4 to 1.5.0 I took a look
at the database and found out it was latin1-encode. I didn't like it
much (if any non ASCII characters are supposed to be allowed in the
database then why should it
On Wed, Mar 25, 2009 at 08:15:51AM +0200, Dan Pascu wrote:
On Tuesday 24 March 2009, Jacek Konieczny wrote:
As I was just doing upgrade from OpenSIPs 1.4.4 to 1.5.0 I took a look
at the database and found out it was latin1-encode. I didn't like it
much (if any non ASCII characters are
