search for: collate

...th auto increment. I checked the mysql log and no attempt is made to change the password. Any idea about the source of the problem? This is my voicemail table: CREATE TABLE IF NOT EXISTS `voicemail` ( `uniqueid` int(11) NOT NULL AUTO_INCREMENT, `te_id` int(11) NOT NULL, `context` char(80) COLLATE utf8_unicode_ci NOT NULL DEFAULT 'default', `mailbox` char(80) COLLATE utf8_unicode_ci NOT NULL, `password` char(80) COLLATE utf8_unicode_ci NOT NULL, `fullname` char(80) COLLATE utf8_unicode_ci DEFAULT NULL, `email` char(80) COLLATE utf8_unicode_ci DEFAULT NULL, `pager` char(80)...

...safeshutdown=yes [mysql] usegmtime=no loguniqueid=yes loguserfield=yes accountlogs=yes I created the table in the DB so: CREATE TABLE IF NOT EXISTS `cdr` ( `id` int(11) unsigned NOT NULL AUTO_INCREMENT, `calldate` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `clid` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', `src` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', `dst` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', `dcontext` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', `lastapp` varchar(200) COLLATE utf8_bin NOT NULL DEFAULT...

Hello. Voice quality when calling - this is one of the most important in the PBX. You need to record the quality parameters for each call to improve. Because the overall quality of a call can only be determined upon completion, I did it in the HangUp handler and wrote in custom fields of CDR. This worked well in asterisk 11. In asterisk 13 I did not find a handler after the call, but before

For sometime now I have not been able to print Collated pages on windows client machines Domain Wide. Our print server is cups, running on Linux Gentoo. If I print directly to the printer within windows I am able to collate. If a Linux machine prints from command line specifying Collate=True while printing pages it works. I have been searching quite so...

...cally). I've tried to pick up on how to ensure the right collation when building R Packages by reading some previous posts and as far as I understand I've basically got two options here: 1) Put all class defs in one script, e.g. allClasses.R. 2) Manually specify the collation via the "Collate" field in the DESCRIPTION file. I'm used to organizing my classes, generics, methods etc. on a "one-per-script" basis in various subdirectories (e.g. R/classes, R/methods etc.) and try automate manual steps wherever possible (not sure if that's the way most of you guys code,...

...queid=yes > loguserfield=yes > accountlogs=yes > > I created the table in the DB so: > > CREATE TABLE IF NOT EXISTS `cdr` ( > `id` int(11) unsigned NOT NULL AUTO_INCREMENT, > `calldate` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', > `clid` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `src` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `dst` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `dcontext` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `lastapp` varchar(200) COLLATE u...

Hi! I have ran on problem with collations. In database.yml I have set: encoding: utf8, but when in console run: >> ActiveRecord::Base.connection.collation => "latin1_swedish_ci" It is Rails 2.1, mysql gem 2.7, mysql 5.1.22. This leads to errors like: Mysql::Error: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation

Any thoughts on how to avoid this problem? Already tried: 1. Setting the charset and collation in migration 001 - no effect: def self.up db_name = ActiveRecord::Base::connection.current_database() execute "ALTER DATABASE #{db_name} CHARACTER SET utf8 COLLATE utf8_bin" end 2. Setting the charset and collation on each table individually - no effect: {:options=>"engine=InnoDB CHARACTER SET utf8 COLLATE utf8_bin"} Note that development and production environments work fine with database default, migration 001, or setting per each t...

...queid=yes > loguserfield=yes > accountlogs=yes > > I created the table in the DB so: > > CREATE TABLE IF NOT EXISTS `cdr` ( > `id` int(11) unsigned NOT NULL AUTO_INCREMENT, > `calldate` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', > `clid` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `src` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `dst` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `dcontext` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `lastapp` varchar(200) COLLATE u...

Hello everyone, I am trying to activate Music On Hold using DB on Asterisk 13. It works fine but in order to use new Music On hold definitions I have to reload the moh module. - The following is my configuration in extconfig.conf - I added the following line: musiconhold.conf => mysql,asterisk,bit_ast_config - The following is the table in the database: mysql> select * from

[crossposted to -stable and -i18n, replies directed to -stable] Hi everyone, could someone point me to infos regarding Unicode collation support in FreeBSD? All I could find was https://wiki.freebsd.org/KonradJankowski/Collation but that page has not been changed in more than two years. Looking at sources of -current it doesn't look like those changes made it into the source tree yet.

...ided to go way with second table CREATE TABLE `cdr_extended` ( `id` int(11) unsigned NOT NULL AUTO_INCREMENT, `uniqueid` varchar(32) NOT NULL DEFAULT '', `callid` varchar(256) NOT NULL DEFAULT '' COMMENT 'sip call-id', `hangupcause` varchar(10) CHARACTER SET utf8 COLLATE utf8_czech_ci NOT NULL COMMENT 'info about hangup', `peerip` varchar(15) CHARACTER SET utf8 COLLATE utf8_czech_ci NOT NULL, `recvip` varchar(15) CHARACTER SET utf8 COLLATE utf8_czech_ci NOT NULL, `from_u` varchar(30) CHARACTER SET utf8 COLLATE utf8_czech_ci NOT NULL, `uri` varc...

...queid=yes > loguserfield=yes > accountlogs=yes > > I created the table in the DB so: > > CREATE TABLE IF NOT EXISTS `cdr` ( > `id` int(11) unsigned NOT NULL AUTO_INCREMENT, > `calldate` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', > `clid` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `src` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `dst` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `dcontext` varchar(80) COLLATE utf8_bin NOT NULL DEFAULT '', > `lastapp` varchar(200) COLLATE u...

Hello, I want to change the connection collation that rails uses but I''m unsure of exactly what the best way to do this is. Everything in MySQL - the server, database and all tables are set to utf8_unicode_ci collation, but the connection collation in rails still appears to be utf8_general_ci (the default?). We are using the mysql2 adapter. I''ve seen a couple of possible

One issue left for me to figure out is that in different languages there are different characters and Xapian takes only english characters. Thefore many word entered by users that contains their own language special characters will not return any result. MySQL offers different collations ... Now when I see how much data Xapian can search perhaps I could expand my index spider different European

Hello, I am having this mysql error in my ruby on rails application. ActiveRecord::StatementInvalid occurred in > event#lg: > Mysql::Error: Illegal mix of collations > (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for > operation ''='': select * from locations where country = ''HU'' and > geo_state = ''08'' and city

...omeone should look into it. Sorry I haven?t taken the time to read >>>> the source code myself. >>> >>> Looks like a collation order issue. See ?Comparison. >> >> With the oddity that both platforms use what look like similar locales: >> >> LC_COLLATE=en_US.UTF-8 >> LC_COLLATE=en_US.utf8 > > It's the sort of thing thay I've tried to wrap my mind around multiple times and failed, but have a look at > > http://stackoverflow.com/questions/19967555/postgres-collation-differences-osx-v-ubuntu > > which seems to be esse...

On 5/30/23 17:45, Ben Bolker wrote: > Inspired by this old Stack Overflow question > > https://stackoverflow.com/questions/19765610/when-does-locale-affect-rs-regular-expressions > > > I was wondering why this is TRUE: > > Sys.setlocale("LC_ALL", "et_EE") > grepl("[A-Z]", "T") > > TRE's documentation at >

The following caused a hard-to-diagnose problem for a user of the survey package. Presumably this is a strange Unicode thing, but is there a convenient reference for how the collation order is determined? I am surprised that adding the same character to the end of two strings of the same length can change the sorting order. in en_US.utf8 locale > "1//"<"10/" [1]

...e realtime database all changes will take effect immediately. The following link explains the difference between realtime and static: https://wiki.asterisk.org/wiki/display/AST/Realtime+Database+Configuration Here is the structure I use: CREATE TABLE `musiconhold` ( `name` varchar(80) COLLATE utf8_unicode_ci NOT NULL, `directory` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `application` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `mode` varchar(80) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `digit` char(1) COLLATE utf8_un...