I use MySQL 4.1 almost exclusively for my work, and was a little bummed
that neither CF 6.1 nor CF7 support the 3.x Connector J driver for
it. You can use the old driver, but you run into issues because
the authentication stuff changed between MySQL 4.0 and 4.1, and only
the new 3.x drivers support the new authentication. Macromedia's
got a technote
about setting up the new driver with CF, but that's still clunky,
because you have to use the "other" database type when setting up your
datasources. Very clunky and error prone. However, there's a
simple fix.
Inside the CF install there is a file named
'neo-query.xml'. Where exactly it is depends on what version of
CF you installed. In a J2EE install, it's in
/WEB-INF/cfusion/lib. Within that file is all your configured
datasources, as well as the base information for each database
type. A simple matter of changing the MySQL type's driver class
to be the one listed in the technote rather than the current value, and
you can again create MySQL datasources using the 'MySQL' datasource
type, and not have to mess with the 'other' type. All the other
settings can remain the same, though you may want to change the name of
the driver type as well (on CF7 it's "MySQL (3.x)").
Note, the
file is a big-ass one-line WDDX packet, so I'd highly recommend
a decent XML editor, rather than a text editor. I used XML Buddy
for Eclipse (one piece of my Eclipse toolkit); it's outline view makes
decyphering the WDDX enormously easier. There are also various
other neo-XXXXX.xml files in that same directory, all filled with other
settings and stuff that can be played around with. Just be
careful, but if you screw them up, your server might inexplicably stop
working untill you manually undo whatever you did.
Vince from NA just provided some clarification on the 6.2 release and
RC expiration on the BD mailing list. BD.NET is the only edition
that is set to expire on the 31st, and it doesn't expire, it just
reverts to developer edition. The Java editions don't expire
based on dates, they expire based on the trial licenses (never for
free, 30 days for JX, and based on the eval license for the J2EE
edition). So unless you're running BD.NET, the March 31st
deadline isn't a concern.
Of course, after the final 6.2 release, NA is dropping all support for
the RC, so you're better off upgrading sooner than later, but there
isn't the hard deadline to do so.
The final release of BlueDragon 6.2 is due out "very, very soon,"
according to Vince from New Atlanta. Perhaps more important to
those that have been using 6.2 RC is that the RC is set to expire on
March 31st, so you'll have to upgrade any systems to 6.2 before that
date.
I'm excited to see what tweaks and fixes NA has made from the RC to the
final release (since this site and several others are running on the
pre-release version), but I'm a little concerned that the timeframe is
so tight to get the upgrade in. Hopefully no code will break with
the new version, because there isn't going to be much time to fix it.
My PowerBook saga continues. I thought that I'd come up with a
pretty stable system last week: install 10.3 from the install CDs and
don't apply ANY updates. Some of the updaters would be nice to
have, but at least with bare-bones 10.3 allowed me to do things like
boot up. Unfortunately, last night, it decided that it didn't
like running stock 10.3 anymore either.
So now I'm looking at alternative OSes for the machine. Gentoo
Linux seems to be the best candidate from my brief looking. Has
anyone had any experience running Linux on a PowerBook G4, and can
offer tips, tricks, or other guidance?
It's been forever since I've posted, but I'm going to try and get back
to posting at least a couple times a week again. First topic is Sean Corfield's
"Frameworks: Fusebox or Mach-II" talk that he gave last night at the
Seattle CFUG meeting. I'm not sure that's the exact title, but
it's close enough. There were about 20 people there, and the
atmosphere was very relaxed, which was a nice change from the usual
lecture format.
Sean went through a brief overview of the two frameworks, how they were
built, and why certain design decisions were made. Then he demoed
six different versions of a very simple task management app, including
"stock" Fusebox, MVC Fusebox, Fusebox w/ OO, Fusebox w/ Tartan, basic
Mach-II, and Mach-II w/ a "real" OO model. He picked the perfect
app to demo, complex enough to actually show the framework doing it's
job, but simple enough keep the discussion about the framework and not
the app itself.
He also had some very nice graphics detailing in a visual format how
the applications worked, using the two frameworks and various
styles. Very clear and concise, and seemed to get a very good
reaction.
Finally, he ran through some pro and cons of each framework, talked a
little bit about his and Macromedia's use of the two frameworks (MM
standardized on Mach-II, Sean uses Fusebox 4.1 for his non-work stuff),
and then about how to select the proper framework for the job.
All in all, a very enlightening talk, with some good discussion amongst
the group stemming out of it.
