I have been using Code Igniter and Ext JS 4 for several months. In that time, I have created a couple basic templates to display MySQL tables and perform CRUD on those tables. In addition, I have wanted to create some basic admin screens for the Core Igniter configured databases. In my configuration, I have multiple databases defined, using Code Igniter’s built-in support for multiple database access. So, given all of that, I have created a controller that will display all Code Igniter configured databases, list the contained tables, and allow you to display and edit those tables.
Right now the basic template supports simple pagination, as well as Adding, Deleting, and Updating records. While fairly full-featured, it does not yet handle remote sorting. In addition, I am sure you will find some minor display issues with data fields that are not your standard integer or varchar. I will look to address these later. As an added bonus, the template references Ext JS remotely, so you do not need to install Ext JS 4 for these admin screens to work. If you are interested in giving Ext JS 4 a try, this is a great way to explore with it.
One feature of this controller is that the panel for the table admin is dynamically generated. This will allow you to save the created JS file, and modify it to suit your needs. You can easily create very custom screens from this generated template.
If you would like to see updates, or have any issues, leave me a message here and I will try to address them.
You can download the zip file here.
To install, just add the enclosed files to your controllers and views directory and make sure you have a valid database configured.
Determining the number of tables that are contained in a MySQL database is very straight-forward, although it is an often asked question. The simplest way to accomplish this is using the following SQL query. In this query, you will provide the database, and the SQL will access MySQL’s internal data scheme (information_schema).
SELECT count(*) as ‘Tables’, table_schema as ‘Database’
WHERE table_schema= ‘The Database Name’
GROUP BY table_schema
If you need to retrieve this information using PHP, use can use the following code. It creates a connection, runs the query, and returns the number of rows retrieved. This query you notice is slightly different than the one above, often there are multiple ways to get the same result!
$conn = mysql_connect(‘localhost’, ‘USERNAME’, ‘PASSWORD’, 1, 65536);
$res = mysql_query( “select table_name from information_schema.tables where table_schema=’test'”, $conn );
echo mysql_num_rows( $res );
And lastly, there is one more way that you can retrieve the number of tables in a database using PHP and the Show Tables command. In this example, you will need to be connected to a server, and have the database set to the one you are querying against.
$tbl_List = mysql_query(“SHOW TABLES”);
while($tables = mysql_tablename($tbl_List,$i))
echo “<br />Table count = $i”;
What database does Facebook use is one of the most common questions asked when folks start taking about what database is the most scalable for large scale web applications. In fact, it is usually a person who is an open source proponent, and knows very well that Facebook uses MySQL as their core database engine. Because of this fact, this is often the single biggest reason that developers use to push to get MySQL used in their company. I would imagine that is why it is a very popular Google query.
While Facebook uses MySQL, they do not use it as-is out of the box. In fact, their team has submitted numerous high-performance enhancements to the MySQL core and Innodb plug-in. Their main focus has been on adding performance counters to Innodb. Other changes focused on the IO sub-system, including the following new features :
- innodb_io_capacity – sets the IO capacity of the server to determine rate limits for background IO
- innodb_read_io_threads, innodb_write_io_threads – set the number of background IO threads
- innodb_max_merged_io – sets the maximum number of adjacent IO requests that may be merged into a large IO request
Facebook uses MySQL as a key-value store in which data is randomly distributed across a large set of logical instances. These logical instances are spread out across physical nodes and load balancing is done at the physical node level. Facebook has developed a partitioning scheme in which a global ID is assigned to all user data. They also have a custom archiving scheme that is based on how frequent and recent data is on a per-user basis. Most data is distributed randomly. Amazingly, it has been rumored that Facebook has 1800 MySQL servers, but only 3 full-time DBAs.
Facebook primarily uses MySQL for structured data storage such as wall posts, user information, etc. This data is replicated between their various data centers. For blob storage (photos, video, etc.), Facebook makes use of a custom solution that involves a CDN externally and NFS internally.
It is also important to note that Facebook makes heavy use of Memcache, a memory caching system that is used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce reading time. Memcache is Facebook’s primary form of caching and greatly reduces the database load. Having a caching system allows Facebook to be as fast as it is at recalling your data. If it doesn’t have to go to the database it will just fetch your data from the cache based on your user ID.
So, while “What database does Facebook use?” seems like a simple question, you can see that they have added a variety of other systems to make it truly web scalable. But, still feel free to use the argument, “MySQL is as good or better than Oracle or MS SQL Server, heck, even Facebook uses it, and they have 500 Million users!”.
Want a quick and dirty way to Truncate all the tables in a MySQL DB? You can use the following one line script.
mysqldump -ppassword YourDBName –no-data dumpfile | mysql dumpfile
What this does is uses mysqldump to output all the tables in the database “YourDBName” into a dump file. This dump file contains drop statements, and create table statements for each table in the database. What this effectively does is drops every table, and recreates it WITHOUT any data inside. Be very careful, since this is a very powerful script, it has the ability to completely wipe out your database with no hope of recovery unless you have a current backup.
For additional ways to execute specific commands against all tables in a DB, look into using mk-find in Maatkit, it is an excellent tool for advanced MySQL scripting.
There are multiple ways in which to remove all data from a MySQL Table.
The first is to use the DROP TABLE command, which will remove the entire table with data. This basically removes the entire table, you will not be able to recover the structure or data.
The second is DELETE * FROM Table which will remove the data, leaving the auto-increment values alone, as well as the rest of the table structure. This method is very slow on large tables using Innodb. This is because each record has to be written to the log. In general, you should never use this method to remove all data from a table.
The third method is to issue a TRUNCATE TABLE command which will quickly remove all the data from the table, reset the auto-increment values (but leave them as auto-increment columns, so they will just start at 1 and go up from there again).
Lastly, you can use the nuclear option, which is as follows :
mysqldump -ppassword YourDBName YourTblName –no-data dumpfile | mysql dumpfile
This will drop the table, and then recreate it all from scratch.
Have you ever seen the dreaded MySQL Error number 1045 Access denied for user ‘root’@’localhost’ (using password: YES)?
Don’t worry, this is an easy to recover from situation. Just follow these basic steps to reset the root user password.
Stop the MySQL server process.
Start the MySQL server process with the –skip-grant-tables option. This option causes the server to start without using the privilege system at all, which gives anyone with access to the server unrestricted access to all databases. BEWARE! Anyone can access your server, so make sure off the Internet, and that you perform the following steps as quickly as possible.
Start the MySQL console client with the -u root option. Mysql -u root
SELECT * FROM mysql.user;
UPDATE mysql.user SET Password=PASSWORD(‘[password]’) WHERE User='[username]’; Replace [username] with root to change root. You can also change any other user as well.
Stop the MySQL process
Start the MySQL Process normally (i.e. without the –skip-grant-tables option).
Some folks have reported that issuing a Flush Privileges command will prevent your having to perform the final Stop/Start of the MySQL server. However, this has not always worked for me, and I think to be safe, it is wise to recycle the server.