#2036 (ok 2.8.0) cannot display capitalised `Database` tables

[McClie]

If a database begins with a Capital, e.g., "Views" or "Hist" no tables are
displayed. Other databses work normally. This is not a problem for 2.7.0-
pl2.

[Jürgen Wind]

Logged In: YES
user_id=1383652

no problem with pma280rc1
win / mysql 5.0.18 &
linux/mysql 4.1.11
here.

pma on win-server can only create databases in lowercase,
but displays it correktly, if create otherwise.

Tables : no restrictions at all.

[Jürgen Wind]

Logged In: YES
user_id=1383652

sorry,
i was a bit confused,
instead of databases read tables.

[Jürgen Wind]

Logged In: YES
user_id=1383652

'Cannot display Capitalised Databases'

should be

'Cannot display Capitalised Tables'

i could confirm that under windows.

------
export is ok:

-- phpMyAdmin SQL Dump
-- version 2.8.0-rc1
-- http://www.phpmyadmin.net
--
-- Host: localhost:9306
-- Erstellungszeit: 22. Februar 2006 um 13:56
-- Server Version: 5.0.18
-- PHP-Version: 5.1.2
--
-- Datenbank: `Test2`
--

-- --------------------------------------------------------

--
-- Tabellenstruktur für Tabelle `Testtable` «-------OK
--

CREATE TABLE `testtable` (
`TestField` varchar(22) NOT NULL default ''
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

--
-- Daten für Tabelle `Testtable` «-------OK
--

INSERT INTO `Testtable` (`TestField`) VALUES ('test');

-- --------------------------------------------------------

--
-- Tabellenstruktur für Tabelle `newtable`
--

CREATE TABLE `newtable` (
`Field1` varchar(22) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

--
-- Daten für Tabelle `newtable`
--

INSERT INTO `newtable` (`Field1`) VALUES ('test');

[Jürgen Wind]

Logged In: YES
user_id=1383652

under Linux:
Display OK
-----
export:
-- phpMyAdmin SQL Dump
-- version 2.8.0-rc1
-- http://www.phpmyadmin.net
--
-- Host: slv12-tux
-- Generation Time: Feb 22, 2006 at 02:27 PM
-- Server version: 4.1.10
-- PHP Version: 5.0.5
--
-- Database: `Test2`
--

-- ---------------------------------------

--
-- Table structure for table `TesttableG`
--

CREATE TABLE `TesttableG` (
`F1` varchar(22) collate latin1_german2_ci NOT NULL default ''
) ENGINE=MyISAM DEFAULT CHARSET=latin1
COLLATE=latin1_german2_ci;

--
-- Dumping data for table `TesttableG`
--

-- -------------------------------------

--
-- Table structure for table `testtable`
--

CREATE TABLE `testtable` (
`TestField` varchar(22) NOT NULL default ''
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

--
-- Dumping data for table `testtable`
--

miraculously data are missing,
but thats onother story...

[Sebastian Mendel]

Logged In: YES
user_id=326580

What is the value of your lower_case_table_names variable in
MySQL server variables?
What is MySQL server version?
Did you recently upgarded your MySQL or are this tables
created before your MySQL server was upgraded to 4 or 5?

Seems either be missconfiguration or a bug of your MySQL server.

http://dev.mysql.com/doc/refman/5.0/en/name-case-sensitivity.html

[Sebastian Mendel]

Logged In: YES
user_id=326580

I assume you are using windows as your MySQL server OS?

[Jürgen Wind]

Logged In: YES
user_id=1383652

as far as i am concerned,
i'm running several mysql-servers on win and linux.
it's a matter of pma280, as the McClie already
mentioned: pma270 is ok!
in mysql capitalized tablesnames are not forbidden,
so pma should be aware of that.
i personally dont use them anyway, but we dont have
controll about the end-users.
----
pma280 sql shows :

SQL query:SHOW TABLE STATUS
Name Engine Version Row_format Rows Avg_row_length
Data_length Max_data_length Index_length Data_free
Auto_increment Create_time Update_time Check_time
Collation Checksum Create_options Comment

Testtable MyISAM 10 Dynamic 1 20 20 281474976710655 1024 0
NULL 2006-02-22 13:11:46 2006-02-22 13:11:48 NULL
latin1_swedish_ci NULL

newtable MyISAM 10 Dynamic 1 20 20 281474976710655 1024 0
NULL 2006-02-22 13:55:39 2006-02-22 13:56:07 NULL
latin1_swedish_ci NULL

[Sebastian Mendel]

Logged In: YES
user_id=326580

@windkiel: of course, but using the MySQL in this way cann
lead too much more trouble than only 'no tables' displayed
in phpMyAdmin - read the given documentation carefully!

http://dev.mysql.com/doc/refman/5.0/en/name-case-sensitivity.html

The Problem is different return of the Databasename:

SHOW DATABASES or information_schema.SCHEMATA gives `Test`
but
information_schema.TABLES gives `test`

so phpMyAdmin cannot find tables for `Test`

so this seems to bee also a bug in MySQL

[Sebastian Mendel]

Logged In: YES
user_id=326580

added workaround, pls test CVS

[Sebastian Mendel]

Logged In: YES
user_id=326580

opend bug at MySQL

http://bugs.mysql.com/17661

[Jürgen Wind]

Logged In: YES
user_id=1383652

Hi Sebastian,
your workaround works very well !

[McClie]

Logged In: YES
user_id=1454716

Sorry since posting this I have been away. I'll try to answer the various points.
1. I am using OSX, using HFS+ partitions (i.e., the server is run from case-
insenstive BSD-like unix)
2. This is about databases, I do not have any capitalised tables. Views was
capitalised to keep it at the head of the list (Capital first sorting works in pma
in the sidebar, but not in the main window).
3. Questions about my MySQL version (5.0.18-standard) seems irrelevant, as
this is a problem unique to pma 2.8.0, no such problems in 2.7.0, or any of
the versions of Cocoa-MySQL or YourSQL that I have run recently. This
problem with 2.8.0 occured after I had been running 5.0.18-standard for a
while, but I made the bug report pretty much the day I downloaded 2.8.0. The
two offending databases (since dumped and reloaded as lower case) would
have been created after the upgrade to 5.0 GA, as there were no views in
MySQL 4, and I only use GA. I have just created a new database Fews and
populated it with one view and one table, same problem in 2.80, Same lack of
a problem in 2.7.0, Cocoa-MySQL and YourSQL (and MySQL Query Browser).
4. I've read the manual link givven by cybot_tm. It seems to refer to
portability of SQL scripts and not to any intrinsic problem with capitalisation.
This server is only ever connected to from OSX so I cannot comment. If
5. lower-case_table_names set to 2, the OSX default. Problem is the same
whether using InnoDB or MyISAM tables.
PS, as an added problem with 2.8.0, when I tried to use rename_database in
pma 2.8.0, it failed with the error that it could not find the table Hist.Hist (or
Views.Views). Of course it couldn't find it, they did not exist, and it was never
asked to find them. Again no such problem with 2.7.0.

Thanks for the repsonse, sorry for the delay in responding.

[Sebastian Mendel]

Logged In: YES
user_id=326580

@mcclie:

1. can you please confirm the bug for your OS here:
http://bugs.mysql.com/17661

3. no its NOT irrelevant as it is a bug in MySQL (phpMyAdmin
introduced using information_schema with 2.8.0)

4. no, it refers to case sensitivity all around in MySQL,
responsible in every query and information_schema

summary: the error comes not from phpMyAdmin, phpMyAdmin
started using information_schema with 2.8.0 and
information_schema returns different cases for the same
table-name.

pls compare your
`information_schema`.`SCHMETA`.`SCHEMA_NAME` and
`information_schema`.`TABLES`.`TABLE_SCHEMA` and your
directory for this Database.

did you tested latest CVS if this problem still exists?

[McClie]

Logged In: YES
user_id=1454716

Added comment about OSX to the MySQL Bug report. CVS workaround works
fine. Many thanks, although I will keep my databases lower case in future, as I
had to when using postgresql.