MySQL Bugs: #22936: Confusing difference(??) in backup definiton from 1.2.3rc versus 1.2.4rc

Bug #22936	Confusing difference(??) in backup definiton from 1.2.3rc versus 1.2.4rc
Submitted:	3 Oct 2006 13:22	Modified:	11 Oct 2006 15:02
Reporter:	Heinz Schweitzer (Gold Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.4 RC	OS:	Windows (XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:

Confusing difference(??) in backup definiton from 1.2.3rc versus  1.2.4rc 
Probably not a bug just my confusion.

MySQL Administrator 1.2.4 RC (German)

MySQL-Server-Information
--------------------------------------------------------------------------------
Mit MySQL-Serverinstanz verbunden
  Benutzername:            root
  Hostname:                localhost
  Port:                    3306
--------------------------------------------------------------------------------
Serverinformation
  MySQL-Version:           MySQL 5.0.18-nt via TCP/IP
  Netzwerkname:            localhost
  IP:                      127.0.0.1
--------------------------------------------------------------------------------
Clientinformation
  Version:                 MySQL Client Version 5.0.11
  Netzwerkname:            hgs
  IP:                      192.168.2.5
  Betriebssystem:          Windows XP
  Hardware:                Intel(R) Pentium(R) 4 CPU 2.00GHz, 504 MB RAM

How to repeat:
Prerequisits:
=============
Make sure you have a simple backup defined with version 1.2.3rc
with settings like in screenshot ab1
NOTE: The checkbox for'Nicht den vollen Pfad schreiben' is not checked. 
============

Open MySQL Administrator 1.2.4 RC (German)
Select (above) Backup
You immediatly get a (new) warning box like in screen shot ab3,
telling something about having enabled fully qualified fieldnames etc...
NOTE: Text not localized

Now look at screen shot ab1. This is from the backup definiton
made in 1.2.3rc. There you see that this field is localized to German and 
telling the exact oposite, to NOT enable fully qualified fieldnames when
checkbox is checked.

The essence out of this is to avoid any negation like 'nicht den vollen
Pfad schreiben' at least in German.

ab1

Attachment: ab1.png (image/png, text), 58.99 KiB.

ab3

Attachment: ab3.png (image/png, text), 112.11 KiB.

Thank you for the report.

Verified as described.

This option was confusing as it was before (which full path?, what has a path to do with the backup?, a path is associated with files on computers). So we decided to make it clearer by making it a positive action (check it if you want it enabled) and give it a better description (now: "Fully Qualified Identifiers"). This has been localized in German to: "Qualifizierte Bezeichner" ("Vollständig" was not added as german strings are generally significantly longer than english ones).

Of course this change has no effect on existing backup projects. In fact, even the same option is written back as bevor, just the way it is presented to the user is now changed.