Export to SQL broken

User, date Message
Written by kalvaro
11 months ago
Category: General
457 posts since Thu, 29 Nov 07
The new "Group objects by type" feature introduced a side effect. Export to SQL no longer works. It seems that HeidiSQL tries to export the groups themselves, rather than the individual items:

-- --------------------------------------------------------
-- Host: 217.116.29.183
-- Server version: 5.0.32-Debian_7etch5-log - Debian etch distribution
-- Server OS: pc-linux-gnu
-- HeidiSQL version: 7.0.0.4164
-- Date/time: 2012-07-20 08:41:33
-- --------------------------------------------------------

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET NAMES utf8 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;

-- Dumping structure for unknown, should never appear foo.Tables
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Tables`;
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Tables`;


-- Dumping structure for unknown, should never appear foo.Views
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Views`;
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Views`;


-- Dumping structure for unknown, should never appear foo.Procedures
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Procedures`;
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Procedures`;


-- Dumping structure for unknown, should never appear foo.Functions
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Functions`;
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Functions`;


-- Dumping structure for unknown, should never appear foo.Triggers
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Triggers`;
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Triggers`;


-- Dumping structure for unknown, should never appear foo.Events
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Events`;
DROP UNKNOWN, SHOULD NEVER APPEAR IF EXISTS `Events`;
/*!40101 SET SQL_MODE=IFNULL(@OLD_SQL_MODE, '') */;
/*!40014 SET FOREIGN_KEY_CHECKS=IF(@OLD_FOREIGN_KEY_CHECKS IS NULL, 1, @OLD_FOREIGN_KEY_CHECKS) */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

Written by ansgar
11 months ago
4027 posts since Fri, 07 Apr 06
Oh yes, nice effect, sigh...
Written by ansgar
11 months ago
4027 posts since Fri, 07 Apr 06
Should be fixed in r4165, hopefully.
 

Please login to leave a reply, or register at first.