When I attempted to connect my 4.3.4 server to the database I recieved the familiar
2012-07-11 16:47:10 ERROR: DatabasePool world NOT opened. There were errors opening the MySQL connections. Check your SQLDriverLogFile for specific errors.
2012-07-11 16:47:10 ERROR: Cannot connect to world database 127.0.0.1;3306;trinity;trinity;world
error. I read through the FAQ, I have set up a number of 3.3.5 servers over the last year and a half, I knew it had to do with DB updates, so I followed the guide at: http://collab.kpsn.org/pages/viewpage.action?pageId=1704351
Yet, no matter what I did, I couldn't get the server to connect. On a hunch, I decided to pull the sql files from /sql/updates/world, which I knew the guide said explicitly not to. When I did, I recieved a ton of errors in my SQL console, but now the world server was connecting to the DB. The data is completely non functional, even worse than the usual alpha bugs the 4.3.4 branch has, but I'm wondering why did it only connect when I imported updates I'm not supposed to import? How do I get it to connect with the proper DB?