This OpenBD deployment is dedicated to Mura, so there's only the one
DS for the Mura MySQL data, and that one checks out fine.
I checked bluedragon.xml, and there's no "phantom" DS in there either.
I was taking no DSN related action recently (well, ever!.. since
installing Mura on this webapp last Sept).
I just upgraded the lib directory and there it is. I thought it might
have been part of some new var or feature storage gizmo in 1.4 - which
is why I even posted it at all.
Now, it's entirely possible that this little gem of a log entry was in
pre-upgrade startups and I never noticed.
So, if nothing else ever breaks... I can live with it.
Al
On 12/5/2010 6:46 PM, Matthew Woodward wrote:
Do you know which datasource it's complaining about? Have you tried
deleting and recreating the datasource?
--
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
