I do not get any feedback of any kind. The die error is not even triggered.
The program runs fine until it gets to this line and then just stops. Anything past the connect line is not executed and I am given no feedback from the connect line whatsoever.
I am wrong in saying that if the db details were wrong then the die command would be executed?
any further ideas?
| [reply] |
Are you running this from the command line or a browser ?
- Browser : run it from the command line. If you are calling <code lang="perl">die()</code> before you print a header, the prowser would print nothing.
- Command line : It appears that there is still something wrong with a path setup somewhere, and the mysql.so file is not getting loaded. It usually will not go into a black hole like that (it usually prints a cannot load message like make test did), but i have seen DBD::Sybase do this on rare occasion. So, back to the path issue from your other posts
i had a memory leak once, and it ruined my favorite shirt.
| [reply] [d/l] [select] |
Just to Say that it is now fixed!
If anyone is having problems installing mysql DDBD on Suse use Msql-Mysql module instead of the DBDmysdql module. Its quite tricky getting DBD::mysql to install succesfully on Suse.
Install the Msql-Mysql module by performing a 'make install && make test'.
Thanks to all who helped.
costas
| [reply] |
eeer, looking at the code the guy posted I think it's clear he is printing a header.
pay attention children.
| [reply] |