I've used Neuromancer
(from Rob Rohan)
on several projects, and I finally decided to implement form posts, in
addition to the raw posts that it already supports. Like it
should be with a well designed library, adding the new functionality
was a snap. I forwarded the changes to Rob, and I'd expect them
to be in the next Neuromancer release, which will be coming out
approximately whenever he feels like it. He just got married
though, so he's got more important things to do than deal with code, so
don't hold your breath. If anyone is interested in
the mods in the meantime, I'd be happy to pass them along directly.
Monthly Archive for August, 2005
I wrote an INSERT query today (for the first time in months), and
missed a comma between two of my values. I also missed one of the
columns in the column list, so there while there was an extra value,
two of them weren't separated by a comma. Something like this (though with CFQUERYPARAM, of course):
INSERT INTO mytable
(id, name)
VALUES
(#id#, #name# #email#)
Now where it gets weird is that MySQL happily ran the statement without error, and concatenated the two values together and inserted the result in the appropriate column (all were varchar). Weird.
Not
sure on whom the blame should reside (possibly me?), but wanted to give
a heads up. And to say that generated SQL is better than hand
writing it. ;)
On Friday morning, my wife gave birth to our second child, Emery Isaac Boisvert.
8 pounds, 1 ounce, 20.5 inches long, and with thick black hair.
Mom and baby are doing well, as came home from the hospital this
afternoon.
As is pretty common knowledge, CFMX 6, CFMX 7, and BD all ship with
JDBC drivers for MySQL 3.x. There have been several posts (here's
one from Steven Erat)
about installing MySQL Connector/J 3.x, which is the driver for MySQL
4.x. In particular, it supports the new authentication scheme
that was introduced in the 4 series.
I've done this on several
servers with great success, but I ran into a little problem a couple
days ago, and thought I'd share. MySQL stores 0000-00-00 00:00:00
as the default value for NOT NULL DATETIME columns. With the
default MySQL drivers, that gets converted to November 30th 0002, but
with the updated drivers, it throws a date format exception. I
can't say for sure if it happens all the time, but at least sometimes.
With
a properly designed app and schema, this shouldn't be a problem (since
those values should be NULL, not the "zero" date), but if you've got
garbage lurking, it's definitely worth a careful look if you're
considering the updated drivers.
