Ticket #5811 (closed Bugs: fixed)

Opened 1 year ago

Last modified 1 year ago

EndPointManager SQL update with latin1 charset force breaks DB update when other tables are in utf8

Reported by: jasb Assigned to: tm1000
Priority: blocker Milestone: 2.11
Component: Endpoint Manager (OSS) Version: 2.10-branch
Keywords: Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

Howdy,

For my particular case, I have a custom setup, with Asterisk, and freepbx 2.10, with all database tables (MySQL) with utf8 charset.

What happened? It didn't updated the database 'cause of the charset missmatch.

What I suggest is on every new table the force for "latin1", the ") ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=48";"

Could the force (DEFAULT CHARSET=latin1) for latin1 be removed?

This way, the table will gain the Database default charset.

Change History

06/07/12 18:17:38 changed by tm1000

  • status changed from new to closed.
  • resolution set to fixed.

Fixed in 2.10.4.1