|
Binod and Sivakumar have been driving the work on JSR 322: JavaTM EE Connector Architecture 1.6, a lesser-advertised but quite important part of the forthcoming Java EE 6 standard. The overall goal is to strengthen the existing 1.5 version of the specification. More details are available in this entry by Siva. It includes Generic Inflow Context, Security Inflow, some Ease of Development, and more. Comments on the Early Draft are accepted for a few more days, until September 8th (in case you're looking for something to read this week-end! :). |
Excited with the release of the MySQL Connector/C++, I thought I’d get it going on Mac OS X.
You’ll first hit the problem that Mac OS X doesn’t come with CMake. So you’ll have to download it from the site - there’s a warning there that the .dmg installer only works for Tiger, but I ran it on Leopard, and its just fine. Don’t forget to allow it to create links in /usr/bin for ease of use.
After that, you will need to install glib. But to get glib going, you need some dependencies:
Installing them is simple: untar (tar -zxvpf package.tar.gz), ./configure, make, then a sudo make install.
Now, the README file or the instructions on the wiki will just work. I have several MySQL installations, so I preferred to specify what cmake found. I did this by:
cmake -D MYSQL_DIR:PATH=/usr/local/mysql/ -D GLIB_DIR:PATH=/usr/local/lib/glib-2.0/ .
Then a simple make, and you can go on and try the examples, in examples/. Try the connect application to make sure things are working. You will probably run into a snag though:
luna:examples ccharles$ ./connect
Connector/C++ connect basic usage example..
ERR: MySQL_DbcException in /Users/ccharles/code/mysql_connector_cpp_1_0_0_preview/examples/connect.cpp((function n/a)) on line 159
ERR: Cannot connect (MySQL error code: 0 )
Take a look at examples/examples.h, and look at the connection properties. It uses the test database, on localhost (127.0.0.1), standard port 3306, user is root, and the default password set there is root too. This may not be the commonest setting, so don’t hesitate to change the password or leave it blank (ala a default install), and rerun make. The sample applications will now work :)
Congratulations to Andrey, Ulf, and the rest of the connectors team in getting this going!
Yes, I know. JavaOne is about Duke, the friendly mascot of Java technology. Created and maintained by James Gosling and all.
But MySQL also introduces Sakila to the JavaOne attendees. Sakila is also friendly, and the mascot of MySQL technology. The dolphin was chosen by MySQL founders Michael “Monty” Widenius and David Axmark, as was its name Sakila (which came from a naming contest in the early days).
_Giuseppe_delfiner.jpg)
Together with Giuseppe (in the picture above) and the rest of the MySQL Community Team, I will be handing out incarnations of Sakila (also seen above in the pic) at CommunityOne and JavaOne as follows:
Ah, and rumour has it that Jonathan may pop in during Giuseppe’s presentation!
Come, ask a smart question, interact, and get a Sakila!
User:jeyrb: del.icio.us/network/jey
msft
connectors
User:jeyrb
system:has:via
systemcenter
via:dmcclure
engyro
Followers of the Forum Nokia Developer Discussion Boards saw interesting pre-announcements last month:
Nokia has ported MySQL and PHP to Symbian.

With 165 million cumulative Symbian smartphones shipped since the formation of Symbian and currently 134 Symbian smartphone models commercially available, it would be interesting to see the effects on the 8,134 third-party Symbian applications commercially available by what Nokia calls “PAMP”.
Availability is planned for next month, at the CCNC 2008 (Fifth IEEE Consumer Communications &Networking Conference, 10 - 12 January 2008 in Las Vegas, Nevada).
Johan Wikman of Nokia, who has already ported the Apache web server to Nokia S60, writes in a Forum Nokia thread (emphasis mine):
I can now reveal that we at the CCNC conference in Las Vegas in January, 2008 will demonstrate and release what we call the PAMP stack.
PAMP stands for Personal Apache, MySQL, PHP, so yes, the full LAMP stack will be made available for S60 smart phones. In addition, there will be PHP extension modules that provide access to the core functionality of the phone. And on top of PAMP you can basically install any LAMP based content management system. For instance, Drupal can be installed off the shelf.
Yes, a fair amount of memory is needed and it’s still pretty experimental stuff, but it runs quite nicely on E90.
So, if you are in the neighbourhood, join us in Las Vegas
![]()
Johan
Richard Bloor comments in Symbian Blogs (again, emphasis mine):
At first sight this may seem like an example of porting just to prove it can be done. It does, however, have the potential to create a whole new way of looking at Web application. For example, I’ve recently been evaluating a number of GTD applications. Several of these use PHP and MySQL and it will be interesting to see if they work on PAMP.
As such PAMP could add yet another option for developers to create S60 applications and create a new paradigm for the “off-line” Web. Hopefully by January I’ll have an S60 device with the memory to run this baby.
Sources:
Perhaps its time for me to upgrade my phone?
Today MySQL releases the first beta version of MySQL Connector/ODBC 5.1. This means that Connector/ODBC 5.1 is now feature complete. Go download it!

Connector/ODBC 5.1 is suitable for most MySQL versions in active use today. It works with MySQL 4.1, 5.0, 5.1 and 6.0. If anyone is still on 4.0 or earlier releases, you should have upgraded ages ago; consider Connector/ODBC 5.1 “the final straw”.
As I wrote in September when we released the alpha version,
It is a partial rewrite of the the original MyODBC 3.51 code base, originally developed by Monty and Venu Anuganti, including individual parts of the current 65K ODBC 5 code base.
The new ODBC 5.1 driver, like 3.51, supports all relevant platforms (including Win64). While ODBC mostly is relevant for Windows, we have some (but not many) Linux based ODBC users.
Overall, ODBC 3.51 (released as 3.51.20) is now in a better state than ever. The ODBC QA team has written several hundred new tests. Without doubt, the 3.51 code base is now a good fundament for the new ODBC 5.1 version.
We’ve added a MSI installer for Windows 64-bit and implemented a native Windows setup library. We’ve implemented most parts of the section in my September blog titled “Before ODBC 5.1 goes beta, you can expect the following functions”, except sqlbigint and the native Mac OS X setup library. There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC. Also, the HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
For more details on functionality added and bugs fixed, look for Jim Winstead’s announcement later today.
Our usual warning: Keep in mind that this is a beta release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data.
Thank you to all who’ve tested Connector/ODBC 5.1 so far! And, obviously, we welcome more testing.
References:
Ruby on Rails 2.0 was released last week, “It’s done!“, David Heinemeier Hansson notes.

Ruby on Rails has come a long way since Lenz Grimmer’s interview with DHH in February 2006.
Browsing DHH’s blog, I find snippets (bolding mine) like
Piggy-backing off the new drive for resources are a number of simplifications for controller and view methods that deal with URLs.
As you might have gathered, Action Pack in Rails 2.0 is all about getting closer with HTTP and all its glory.
We?ve also made it much easier to structure your JavaScript and stylesheet files in logical units without getting clobbered by the HTTP overhead of requesting a bazillion files.
Making it even easier to create secure applications out of the box is always a pleasure and with Rails 2.0 we?re doing it from a number of fronts.
Figuring out where your bottlenecks are with real usage can be tough, but we just made it a whole lot easier with the new request profiler that can follow an entire usage script and report on the aggregate findings.

Seems to me like Rails 2.0 goes further still in the direction of the RoR tagline “Web development that doesn’t hurt” and its expanded version
Ruby on Rails is an open-source web framework that’s optimized for programmer happiness and sustainable productivity. It lets you write beautiful code by favoring convention over configuration.
Congratulations, DHH and the Rails Team!
References: