Re: [WebDNA] Cannot get WebDNA and MySQL working.
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 112274
interpreted = N
texte = no prob.DOn Apr 9, 2015, at 8:39 AM, Keith Scarzafava =wrote:> Donovan,>=20> You were correct with where to look. I commented out the handler =in> httpd.conf and I was able to connect to MySQL. Thanks for shove in =the> right direction!>=20>=20>=20> #AddHandler fcgid-script .dna .tpl .html> AddHandler .dna .tpl .html>=20> Keith>=20> =~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=~~> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>=20> -----Original Message-----> From: Donovan Brooke [mailto:dbrooke@euca.us]=20> Sent: Tuesday, April 07, 2015 10:23 AM> To: talk@webdna.us> Subject: Re: [WebDNA] Cannot get WebDNA and MySQL working.>=20> That looks like WebDNA FastCGI.. which some of those builds didn't =support> MySQL.>=20> Donovan>=20>=20> On Apr 7, 2015, at 8:38 AM, Keith Scarzafava =wrote:>=20>> Donovan,>>=20>> Thanks for the advice and assist! Here is the output of the code =you>> provided with some background. The OS is CentOS5.5. I've also made =sure>> SELINUX and the httpd server name was set per the README file. I've>> attempted this on a CentOS6 64bit installation with WebDNA version 8=20=>> and get the same results- so whatever I am missing I am missing it=20>> twice. I was curious to see if a new version would address the =issue.=20>> Anyway, It appears I am not making the connection to the MySQL =server,=20>> just not sure why and there isn't anything in the logs if any use.>>=20>> I've verified I can connect to the MySQL server from the command line=20=>> via mysql and for kicks I set up a DSN. I was originally trying to=20=>> use the native SQL set up, and only went the ODBC avenue just to see=20=>> if I could get anything to work.>>=20>> Output from your code sample.>> =---------------------------------------------------------------------->> ------>> =---------------------------------------------------------------------->> --->> Info:>> Platform: linux unix 32bits>> Product: WebDNA>> Version: 7.1.705>>=20>> INVALID VALUE (MySQL) FOR PARAMETER: type.>> - Please refer to the SQLConnect documentation.>>=20>> If I remove the dbType, which according the documentation, will=20>> default to MYSQL, I get a different error see below:>>=20>> Result with the connection string less the dbtype:>> =---------------------------------------------------------------------->> ------>> ---------------------------------------------->> ERROR: (null) DATABASE CONNECTION FAILED! - (NO IMPLEMENTATION ERROR=20=>> STRING>> PROVIDED)>>=20>> SQLinfo reports: ERROR: COULD NOT FIND SQLCONNECT VARIABLE "conn1".>> - Subsequent SQL commands attempting to use that result ID will fail.=20=>>=20>>=20>> Best,>> Keith>>=20>>=20>>=20>> =~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>> ~~~~~~=20>> =~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>> DISCLAIMER: Any views expressed in this message are those of the=20>> individual sender. This email and any attachments to it may contain=20=>> confidential information and may be legally privileged. If you are=20=>> not the intended recipient, you must not review, transmit, convert to=20=>> hard copy, copy, use or disseminate this email or any attachment to=20=>> it. If you have received this email in error, please immediately=20>> notify the originator by return email and delete this message. Please=20=>> note that if this email contains a forwarded message or is a reply to=20=>> a prior message, some or all of the contents of this message or any> attachments may not have been produced by this office.>>=20>>=20>> -----Original Message----->> From: Donovan Brooke [mailto:dbrooke@euca.us]>> Sent: Monday, April 06, 2015 3:27 PM>> To: talk@webdna.us>> Subject: Re: [WebDNA] Cannot get WebDNA and MySQL working.>>=20>> Keith,>> It's always good to be verbose when posting to a technical forum.=20>> posting code, mysql version, etc...>>=20>> Couple of things..>> ODBC only works with the older (and confusing) [SQL] contexts...=20>> (those tags should be changed to [ODBC], and also checked over to =make=20>> sure they are still robust.. anyway.)>>=20>> If you are testing locally.. plant this template on your server and=20=>> copy / past the results back to the list.>>=20>> *** CHANGE below to your actual password. *********>>=20>> ------START TEMPLATE---------->> >> >> >> > />>> MySQL test>> >> >> Info:
>> Platform: [platform]
>> Product: [product]
>> Version: [version]
>>=20>>=20>> [SQLconnect>> =dbType=3DMySQL&host=3Dlocalhost&database=3Dgallery_inv_management&uid=3Dro=ot&p>> wd=3D> urpass>&conn_var=3Dconn1]>> Connected successfully
>> [/SQLConnect]>>=20>> SQLinfo reports:>> [SQLinfo conn_ref=3Dconn1]>> Host: [SQL_HOST]
>> Server Version: [SQL_SERVERVER]
>> Client Version: [SQL_CLIENTVER]
>> [/SQLinfo]>>=20>> >>