Props for sharing all of the great information, the only problem I have… is now I want to build one.

Perhaps on a miniature scale, 67 terabytes seems a bit excessive.

Click more to see the code.

package org.connect;

import java.sql.*;

public class TestConnect {

public static void main(String[] args)

{

Connection conn = null;

try

{

String userName = “mordy3_test”;

String password = “test”;

String url = “jdbc:mysql://harrisburgvolleyball.com:3306/mordy3_test”;

Class.forName (“com.mysql.jdbc.Driver”).newInstance ();

conn = DriverManager.getConnection (url, userName, password);

System.out.println (“Database connection established”);

}

catch (Exception e)

{

System.err.println (“Cannot connect to database server”);

}

finally

{

if (conn != null)

{

try

{

conn.close ();

System.out.println (“Database connection terminated”);

}

catch (Exception e) { /* ignore close errors */ }

}

}

}

}

• MyISAM — The default MySQL storage engine and the one that is used the most in Web, data warehousing, and other application environments. MyISAM is supported in all MySQL configurations, and is the default storage engine unless you have configured MySQL to use a different one by default.

• InnoDB — A transaction-safe (ACID compliant) storage engine for MySQL that has commit, rollback, and crash-recovery capabilities to protect user data. InnoDB row-level locking (without escalation to coarser granularity locks) and Oracle-style consistent nonlocking reads increase multi-user concurrency and performance. InnoDBstores user data in clustered indexes to reduce I/O for common queries based on primary keys. To maintain data integrity, InnoDB also supports FOREIGN KEY referential-integrity constraints.

• Memory — Stores all data in RAM for extremely fast access in environments that require quick lookups of reference and other like data. This engine was formerly known as the HEAP engine.

• Merge — Allows a MySQL DBA or developer to logically group a series of identical MyISAM tables and reference them as one object. Good for VLDB environments such as data warehousing.

• Archive — Provides the perfect solution for storing and retrieving large amounts of seldom-referenced historical, archived, or security audit information.

• Federated — Offers the ability to link separate MySQL servers to create one logical database from many physical servers. Very good for distributed or data mart environments.

• NDBCLUSTER (also known as NDB) — This clustered database engine is particularly suited for applications that require the highest possible degree of uptime and availability.

  Note

  The NDBCLUSTER storage engine is not supported in standard MySQL 5.1 releases. MySQL Cluster users wishing to upgrade from MySQL 5.0 should instead migrate to MySQL Cluster NDB 6.2 or 6.3; these are based on MySQL 5.1 but contain the latest improvements and fixes for NDBCLUSTER.

• CSV — The CSV storage engine stores data in text files using comma-separated values format. You can use the CSV engine to easily exchange data between other software and applications that can import and export in CSV format.

• Blackhole — The Blackhole storage engine accepts but does not store data and retrievals always return an empty set. The functionality can be used in distributed database design where data is automatically replicated, but not stored locally.

• Example — The Example storage engine is “stub” engine that does nothing. You can create tables with this engine, but no data can be stored in them or retrieved from them. The purpose of this engine is to serve as an example in the MySQL source code that illustrates how to begin writing new storage engines. As such, it is primarily of interest to developers.

Since I’m taking the plunge into Linux (Ubuntu Server 8.10), I thought keeping a running list of useful (and not) Linux commands might be helpful.

Primarily because I forget everything… but also in case anyone else ever actually finds this blog

http://github.com/ – Code hosting in the cloud

http://en.footiefox.com/ – Soccer updates in the browser

http://www.webdigi.co.uk/blog/2009/run-php-on-the-google-app-engine/ – Short tutorial on Quercus and GAE (Google App Engine)

http://www.caucho.com/resin-3.0/quercus/ – Java is attempting to eat PHP

http://www.caucho.com/products/whitepapers/quercus.pdf – Munch munch munch

http://blog.herbert.groot.jebbink.nl/ – PHP/SQL on GAE (Google App Engine), since GAE doesn’t support relational database models… weird

http://code.google.com/p/google-wave-resources/issues/list – Just trying to keep up to date on Wave

http://en.wikipedia.org/wiki/Java_Persistence_API – Interesting… I really need to look-up the differences between Java SE and Java EE

http://blog.caucho.com/?p=196 – Love this line – “Unfortunately, GAE doesn’t support MySQL, or any other relational database for that matter. We’re limited to Google Datastore, which is pretty much a big hash table.”

http://nanotux.com/blog/the-ultimate-server/

Then Symfony, then I’m going to code some schtuff.

I’m thinking about using the LiveUser and LiveUserAdmin package from PEAR

http://www.lighttpd.net/

This looks like fun:

http://stackoverflow.com/questions/420295/why-do-some-pdfs-hang-when-downloading-in-ie-when-served-by-lighttpd

Therefore… I am about to disembark on my most ambitious project yet to date. To make a fully functional app from bottom to top using:

MySQL database -> Java servlets -> AJAX front-end (Using GWT)

This will not be simple, this will not be fast, this will not be fun.

Ready…set…go!

Edit: Crap I jumped the gun, need to learn more about GWT RPC and servlets and how to implement them, hooray!

I went about changing and redefining the following four:
define(’WP_SITEURL’, ‘http://www.freddysmind.com/wordpress’);
define(’WP_HOME’, ‘http://www.freddysmind.com/wordpress’);
define( ‘WP_CONTENT_URL’, ‘http://www.freddysmind.com/wordpress/wp-content’);
define( ‘WP_CONTENT_DIR’, $_SERVER['DOCUMENT_ROOT'] . ‘/wordpress/wp-content’ );

Piece of cake, I thought I was set. But apparently it doesn’t change the wordpress UPLOAD directory. I’m sure it’s the fact that I just missed the post that said I needed to include that as well. All of my uploads were disappearing.

You can change the uploads directory without having to define it in the wp-config.php file.
Simply go under the Dashboard and go to Settings -> Miscellaneous and you can redefine it there.