I was just thinking that perhaps MYSQL didn't do return codes. At least
your grep and replace task can be a bit more automated now!
Not that I a wiz on any single DB platform. I've just always tried to
keep my SQL as generic as possible for portability's sake. Any feature,
bell or whistle beyond - the connection, the call and the result set -
has always met with my suspicion.
It's either a bug or deserves some documentation. I would suggest
popping something here, to keep it on the radar of these fine fine,
overworked heroes: http://code.google.com/p/openbluedragon/issues/list
I suppose you should do a little search first, just to make sure you
found something new.
Al Holden
On 8/11/2010 8:05 PM, Craig328 wrote:
Alan...that did it. Drop the returnCode attribute and the SP ran like
it was supposed to. Hadn't considered that it could be one of the tag
attributes.
There isn't any mention of the attribute not being supported in any of
the openBD docs I have seen. Is this the kind of thing that ought to
be reported?
Thanks again for the suggestion. The version of BD I'm using is 1.3
(2010-04-25 19:34:20 GMT build).
Craig
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
official manual: http://www.openbluedragon.org/manual/
Ready2Run CFML http://www.openbluedragon.org/openbdjam/
mailing list - http://groups.google.com/group/openbd?hl=en
