PlanetMysql.ru – информация о СУБД MySQL

Do you ever stop and think? It happens to me all the time, random subjects kick in and I end up searching (aka googling) and today I wondered … Why is MySQLs logo a dolphin? Shame on me it took me so long to ask the question but as the saying goes, better late than never.

As per MySQLs own article:
“We’ve been discussing a new logo for at least a year”, says main developer and MySQL AB founder Michael “Monty” Widenius. “I am personally concerned about the survival of endangered species, and I liked the idea of the dolphin as soon as it came up. It combines great symbol value with a powerful, modern design.”

After a while the name was chosen out of 6357 suggestions by the community and that is how Sakila the dolphin came to be :) …. and we lived happily ever after (or at least hope to!)

PlanetMySQL Voting: Vote UP / Vote DOWN

It has been a while since I posted on my blog - in fact, I believe this is the first time ever that more than one month passed between posts since I started blogging. There are a couple of reasons for the lag:

• Matt Casters, Jos van Dongen and me have spent a lot of time finalizing our forthcoming book, Pentaho Kettle Solutions (Wiley, ISBN: 978-0-470-63517-9). The book is currently being produced, and should be available according to schedule in early September 2010. If you're interested, you might like to read one of my earlier posts that explains the organization and outline of the book.
  
  (I should point out that we have reorganized the outline as the project progressed, so the final result will not have all the chapters mentioned in that post. We do however cover most of the topics mentioned.)


• I have been checking out Quipu, a promising Open Source data warehouse management solution. Quipu provides a repository-based extensible code-generator that allows you to generate and maintain a data warehouse based on the Data Vault model. One of the things I want to do in the short term is write templates that allows it to work for MySQL, and after that, I want to see if I can get Quipu to generate Kettle Jobs and transformations.


• I have been working on a couple of software projects. Two of them are currently available as open source on google code:

  
  

  mql-to-sql

  This allows you to use the Metaweb Query Language (MQL) to query a RDBMS. If you're wondering what this is all about: MQL is the query language used by Freebase (which is a collaborative "database-of-everything" or "wikipedia-gone-database").
  
  While Freebase is interesting in its own right, I am particularly enthused about the MQL query language. I feel that MQL is an exceptionally good solution for flexible, expressive and secure data access for modern (AJAX) Web applications. Even though MQL was not developed with relational database systems in mind, I think it is a pretty good fit.
  
  Anyway, this is very much a work in progress, and I appreciate your feedback on it. If you're interested, you can read a bit more about my take on RDBMS data access for web applications and MQL on the mql-to-sql project home page. I have also put up an online demo that allows you to query the sakila MySQL sample database using MQL.

  
  

  kettle-cookbook

  This is a project that provides auto-documentation for Kettle (a.k.a. Pentaho Data Integration).
  
  The project consists of a bunch of Kettle Jobs and transformations (as well as some XSLT stylesheets) that extract data from Kettle Jobs and transformation and transform it into a collection of human-readable HTML documents along with a table of contents. The resulting documentation looks and feels a bit like JavaDoc documentation.
  
  If all goes well, I will be presenting kettle-cookbook in a Pentaho web seminar, which is currently scheduled for September 15, 2010

  
  



• I've been enjoying 4 weeks of vacation (I started working this week). There's not much to tell about that, other than that it was great spending a lot of time with my family. I plan to do this more often, and now that Kettle Solutions is finished I should be able to find more time to do it.


• I've been looking at two emerging HTML5 APIs for client-side structured storage, the Web SQL Database API and the Indexed DB API.
  
  I have developed a few thoughts about the ongoing debate (see this and article for some background) about which one is better and I see a role for something like MQL here too. I will probably write something about this in the next few weeks


• Yesterday, I got wind of the JS1k contest! Basically, the challenge is to write an interesting standalone JavaScript demo program that must be no larger than 1024 bytes. It is amazing and inspiring to see what people manage to do with a modern browser in 1k of JavaScript code.
  
  I decided to try it myself, and you can find my submission here: An interactive SQL query tool for the Web SQL DB API.
  
  Essentially, you get a textarea where you can enter arbitrary SQLite queries, and button to execute the SQL, and a result area that will print a feedback message and a result table (if applicable). As a bonus, there's a button to get a listing of the available database objects (using a query on sqlite_master) and an explain button to show the query plan of the current SQL statement.
  
  The demo works on recent versions of Google Chrome, Apple Safari and Opera. It can run offline, and does not require any plugins. I should say that I expect my submission will be rejected by the judges since the demo is not functional on Mozilla Firefox, which is a requirement. (That is, the script will detect that the Web SQL Database API is not supported and print a message to that effect). However, it was still fun to try my hand at it.
  

Ok - that's it for now. I will try and post more regularly and write about these and other things in the near future. Don't hesitate to leave a comment if you have any questions or suggestions.
PlanetMySQL Voting: Vote UP / Vote DOWN

Taking TOTD #121 forward, this blog explains how to create a JPA Persistence Unit for a MySQL sample database and package it as a library. This JAR file can then be easily included in other web applications.

Lets get started!

1. Configure GlassFish for using the MySQL sample database (sakila) as described in TOTD #121.
2. Add the GlassFish instance in NetBeans IDE using "Services" panel.
3. Create JPA entities using NetBeans IDE.
   1. Create a Java class library:
      
      
      
      Our ultimate goal is to create a reusable JAR file and that's why this project type is chosen.
      
   2. Specify the name of project as "SakilaPU":
      
      
      
   3. Right-click on the project and select "New", "Entity Classes from Database ..." to initiate the process of entity generation:
      
      
   4. Choose the database connection as:
      
      
      
      If not configured, then can be easily done by clicking on "New Database Connection ..." in the list box.
      1. Click on "Add All >>" to generate the mapped JPA entities for all tables and views.
      2. The views do not have primary keys and will need to be appropriately annotated (described later).
      3. Click on "Next >".
         
   5. Give the package name as:
      
      
      
      and specify the package name as "sakila". Click on "Create Persistence Unit ...".
   6. Change the default PU name from "SakilaPUPU" to "SakilaPU":
      
      
      
      and click on "Finish". Notice that "EclipseLink", the Reference Implementation of JPA 2.0, is used as the persistence library.
   7. Add "@javax.persistence.Id" annotation to the following class/field combination:

      Class	Field
      sakila.SalesByFilmCategory	category
      sakila.ActorInfo	actorId
      sakila.FilmList	fid
      sakila.CustomerList	id
      sakila.NicerButSlowerFilmList	fid
      sakila.StaffList	id
      sakila.SalesByStore	store

      
      This is required because none of the "views" are defined with a primary key.

   8. Right-click on the project and select "Clean & Build". This generates "dist/SakilaPU.jar" and the structure looks like:

      

This JAR file can now be included in any web application. The pre-built JAR file can also be downloaded here. The key items to note about this pre-built JAR:

• Persistence Unit Name: "SakilaPU"
• All classes are in "sakila.*" package.
• Each class has a pre-defined "<CLASS-NAME>.findAll" named query that returns all elements from the underlying view/table.
• Can be easily added in "WEB-INF/lib" directory of your web application.

Even though this blog uses a MySQL sample database, these steps can be easily followed for any other database such as Oracle or JavaDB.

Technorati: totd javaee glassfish v3 jpa eclipselink persistenceunit mysql sakila netbeans

PlanetMySQL Voting: Vote UP / Vote DOWN

This blog clearly explains how to configure the MySQL sample database (sakila) with GlassFish. Even though the instructions use a specific database but should work for other databases (such as Oracle, JavaDB, PostgreSQL, and others) as well. The second half of the blog provide specific syntax for the Oracle sample database.

1. Download sakila sample database and unzip the archive.
2. Install the database as described here - basically load and run "sakila-schema.sql" and "sakila-data.sql" extracted from the archive.
3. Create a new MySQL user account using MySQL CLI Admin and assign the privileges
   1. Using "root" user (sudo mysql --user root)
      

      CREATE USER glassfish IDENTIFIED BY 'glassfish';
      GRANT ALL PRIVILEGES ON *.* TO 'glassfish'@'localhost' IDENTIFIED BY 'glassfish';
      FLUSH PRIVILEGES;
      

   2. Using "glassfish" user (sudo mysql --user glassfish)

      source sakila-schema.sql;
      source sakila-data.sql;
      

4. Download Connector/J, unzip and copy "mysql-connector-java-5.x.x-bin.jar" to "glassfish/domains/domain1/lib/ext" directory.
5. Start GlassFish server as:

   asadmin start-domain
   
   

6. Create a JDBC resource
   1. Create JDBC connection pool as:

      asadmin create-jdbc-connection-pool --datasourceclassname com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource --restype javax.sql.DataSource --property "User=glassfish:Password=glassfish:URL=jdbc\:mysql\://localhost/sakila" jdbc/sakilaPool
      

   2. Test the JDBC connection pool as:

      asadmin ping-connection-pool jdbc/sakilaPool
      

   3. Create the JDBC resource as:

      asadmin create-jdbc-resource --connectionpoolid jdbc/sakilaPool jdbc/sakila
      

That's it!

Creating a JDBC resource for any other database requires the following updates to the steps mentioned above. Lets consider modifying these steps for the Oracle sample database.

1. Use the client interface SQL*PLus and connect as:
   

   sqlplus "/ as sysdba"
   

   
   create user and grant the privileges as:
   

   CREATE USER glassfish IDENTIFIED BY glassfish DEFAULT tablespace users TEMPORARY tablespace temp;
   GRANT CONNECT TO glassfish IDENTIFIED BY glassfish;
   GRANT UNLIMITED TABLESPACE TO glassfish;
   GRANT CREATE TABLE TO glassfish;
   GRANT CREATE SEQUENCE TO glassfish;
   

2. Copy the appropriate JDBC driver (ojdbc6.jar).
3. Create the JDBC resource as:
   

   asadmin create-jdbc-connection-pool --datasourceclassname oracle.jdbc.pool.OracleDataSource --restype javax.sql.DataSource --property "User=hr:Password=hr:URL=jdbc\:oracle\:thin\:@localhost\:1521\:orcl" jdbc/hr
   asadmin ping-connection-pool jdbc/hr
   asadmin create-jdbc-resource --connectionpoolid jdbc/hr jdbc/hr
   

   
   as explained in TOTD #108.

Here are a few other related entries:

• RESTful representation of sakila using NetBeans and GlassFish

• JPA + Servlet 3.0 Application using Sakila in Eclipse

• JSF + JPA + EJB Application using Oracle, NetBeans, and GlassFish

Technorati: totd javaee glassfish v3 jpa mysql sakila oracle

PlanetMySQL Voting: Vote UP / Vote DOWN