Hello.


I think we may open a bug, but still we have to try to find at least

the command line options with which mysqld has been started. You should find

a place in your startup scripts where mysqld is invoked. Start it with

--log[=file] --log-error[=file] options. Some clues could be found in these

log files.  





"Jason St. Louis" <[EMAIL PROTECTED]> wrote:

> Hi.  Thanks for the response.

> 

> Here is all the relevent information you asked for:

> 

> [EMAIL PROTECTED] mysql]$ ./bin/mysql -u root -p

> Enter password:

> Welcome to the MySQL monitor.  Commands end with ; or \g.

> Your MySQL connection id is 130 to server version: 3.23.55

> 

> Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

> 

> mysql> use gb;

> Database changed

> mysql> show tables;

> Empty set (0.01 sec)

> 

> mysql> show table status;

> Empty set (0.00 sec)

> 

> mysql> show table status from gb;

> Empty set (0.01 sec)

> 

> mysql> select count(*) from player;

> +----------+

> | count(*) |

> +----------+

> |       15 |

> +----------+

> 1 row in set (0.00 sec)

> 

> mysql> select count(*) from gb.player;

> +----------+

> | count(*) |

> +----------+

> |       15 |

> +----------+

> 1 row in set (0.00 sec)

> 

> mysql> Bye

> 

> [EMAIL PROTECTED] mysql]$ ./bin/mysqlshow -u root -p gb

> Enter password:

> Database: gb

> +--------+

> | Tables |

> +--------+

> +--------+

> 

> [EMAIL PROTECTED] mysql]$ ./bin/mysqlshow --status -u root -p gb

> Enter password:

> Database: gb

> +------+------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+----------------+---------+

> | Name | Type | Row_format | Rows | Avg_row_length | Data_length | 

> Max_data_length | Index_length | Data_free | Auto_increment | 

> Create_time | Update_time | Check_time | Create_options | Comment |

> +------+------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+----------------+---------+

> +------+------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+----------------+---------+

> 

> 

> As you can see, it doesn't matter how I go about it, I always get the 

> same result.  I issued the "select count(*) from player" statement to 

> show that even though it doesn't show any tables, I can still perform an 

> sql statement against a table that should be there.

> 

> I do not have a configuration file (I assume you are reffering to the 

> my.cnf file?)  I guess this is something you have to manually create and 

> I suppose I never did that.  I guess that means my mysql server is using 

> all defaults.

> 

> I would just re-install mysql, except that I can't even do a mysqldump 

> to get my data/table structure out of the database because of this 

> problem.  guess I should have been taking backups, eh?

> 

> Is there any other relevant information I can provide that may help?

> 

> Here is the mysql user table entry for the user I am using to perform 

> these statements:

> 

> mysql> select * from user where user = 'root' and host='localhost';

> +-----------+------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+

> | Host      | User | Password         | Select_priv | Insert_priv | 

> Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | 

> Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv 

> | Index_priv | Alter_priv |

> +-----------+------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+

> | localhost | root | -protected------ | Y           | Y           | Y 

>         | Y           | Y           | Y         | Y           | Y 

>        | Y            | Y         | Y          | Y               | Y 

>        | Y          |

> +-----------+------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+

> 1 row in set (0.00 sec)

> 

> 

> Thanks.

> Jason

> 

> Gleb Paharenko wrote:

>> Hello.

>> 

>> 

>> 

>> Sounds very strange. May be there is a bug, and it would be great if someone

>> 

>> corrects me, but I haven't found anything related in bugs database.

>> 

>> You said that you issued "show tables" statement on your database? Maybe 

>> 

>> it would be helpful to try not only "show tables from your_database", but

>> 

>> also:

>> 

>>  use your_database;

>> 

>>  show tables;

>> 

>> or

>> 

>>  show table status;

>> 

>>  show table status from your_db;

>> 

>> 

>> 

>> What output the command line utility mysqlshow produced?

>> 

>>   mysqlshow your_database

>> 

>>   mysqlshow --status your_database

>> 

>> 

>> 

>> When you were making selects did you use db_name.tbl_name syntax to refer to 

>> 

>> a table? Send us your config file (however I don't know if it would be 
>> helpful,

>> 

>> but this is a good practice).

>> 

>> 

>> 

>> "Jason St. Louis" <[EMAIL PROTECTED]> wrote:

>> 

>> 

>>>Hi Folks,

>> 

>>>I've been running a website on php/mysql database for about a year now.  

>>>I typically enter data using the phpmyadmin package.  The other day I 

>>>attempted to add some data but it appeared to phpmyadmin that there were 

>>>no tables in my database.  I connected to mysql using the commandline 

>>>client and issued a "show tables" statement on my database, which came 

>>>back with an empty set.  However, if I run a select statement against 

>>>tables I know should be there, I get results.  So the data is still 

>>>there, I just can't see the tables.  Does anyone have any idea what 

>>>might be causing this?  I am the only one who has access to the database 

>>>so the priveleges for the user should not have changed.  I created an 

>>>additional user with

>>>"Grant all privileges on *.* to 'user'@'host' identified by 'password' 

>>>with grant option;"

>>>and attempted to view the tables with that user, with the same results.

>>

> 

>>>Any ideas?

>>

> 

>>>mysql version is: Ver 11.18 Distrib 3.23.55, for pc-linux (i686)

>>

> 

>>>Thanks.

>>>Jason

>> 

>> 

>> 

>> 

>> 

> 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to